Good thing they never make a mistake when we ask actual questions!
Good thing they never make a mistake when we ask actual questions!
Blame whoever implemented it if you want, but 9 times out of 10 it’s management that’s pushing for a quick fix.
Its a great way to make simple code 300% bigger than necessarily.
I know the second one is better, but I also know I’m terribly inconsistent with this stuff.
Isn’t the point of injecting classes so that you don’t have tens of instances of the same class in memory?
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?
There are other aspects of working remote that go beyond the extra time gained from not commuting. Like not getting interrupted with useless conversations, or distracted by the noise when you need to concentrate or being more comfortable in your own space.
Also what’s the point of going to work in the office if you are just going to have a bunch of meetings online anyway?
I love coding at work, unfortunately 90% of what I do is not coding.
I find inserting text to be extremely confusing.
This needs a bit of work but it could be interesting
You forgot the 3 paragraph WHERE clause to get every data point of a wednesday of an even year of a person who stubbed their toes on a roomba in their parent’s basement.
Then someone needs to change something about the code and doesn’t bother updating the comment. Now you still have uncommented code but with a comment that confuses instead of helping.
I was also like that until I discovered ligatures were thing.
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.
Just like Stadia
That + reader mode is a blessing for articles.
Didn’t deno endup having to incorporate many if the things Node has that they were initially against?
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 ¯\_(ツ)_/¯