At this point it’s probably easier to make a new operating system from scratch(actually, not just forking the linux kernel) than a web engine.

I like stand-up. It’s probably the only time of the day I see my coworkers. Also we don’t do status reports or anything so maybe I’m just lucky ¯\_(ツ)_/¯

Its a great way to make simple code 300% bigger than necessarily.

Backend developer: “The new functionality is done!” PO: Looks at tests “Seems good, ship it!”

Frontend developer: “The new functionality is done!” PO: Looks at his screen “This spacing could be a little to the right, also I think I didn’t really like this text, also it should probably auto-scroll to the top and this button should change colors when I click it and also don’t forget to change the error messages I was happy with before and also I think it should…”

Then they change what the function does without updating the name and you misunderstand the code completely.

It all depends on how much time is spent on them. A few hours a week? No biggie. 3+ hours every single day? Do they think we can develop anything like that?

• Doesn’t expose information
• the service/thread just restarts
• Is an experimental feature
• that’s not enabled by default

Yeah I can definitely see why the devs decided to just fix it on the next patch. Reporting a CVE for this feels very unnecessary.

I love coding at work, unfortunately 90% of what I do is not coding.

I find inserting text to be extremely confusing.

It makes sense to do it like that if you are supposed to test requirements. Depending on the testing tools you have it might not be feasible unfortunately.

As a frontend dev: who knows?