2,957 karma · joined December 6, 2019
Telling a team that "the deadline is May 8th, but the _fake_ deadline is May 1st" doesn't do anything for motivation, and could actually backfire since it's arbitrary. Saying something reasoned like "we need this delivered on May 8th, but we need feature development to be complete by May 1st to allow for a week of testing and deployment rollout" gives meaning to the "fake" deadline and sets up some expectations for what will happen once the "fake" deadline is reached
Of course, with proper planning, these cease to be "fake", so I guess the point is moot
I am worried about my decision too, but I think about a few things:
- You got your current job (plus all of the previous roles), so why wouldn't you be able to do it again if and when the time comes?
- Job gaps don't look as bad as they used to. People understand burnout and being stuck in a bad job. Breaking away from those can be seen as a positive, especially if you are pursuing your own health and interests
- There's more to life than draining your useful waking hours for a paycheck at a place that offers little else. With more time and energy, you can explore interests and projects on your own terms
Best of luck in your future endeavors
I'm curious about people who have done this and how they've handled things like insurance, taxes, and getting back into the workforce after such a long gap. It seems like a big risk since there's no guarantee of employment. I'd also imagine having a long break would be looked on unfavorably by interviewers and make it harder to get back in
Sometimes it's easier to adopt better practices when moving to another team or project altogether
You should also write tests. They ensure that your code works as intended. Some teammates might not understand that untested code can cause more development time since broken features will have to be fixed in production, so highlighting bugs that have to be fixed as well as writing tests thst cover as many cases as possible should shine some light for those still not understanding their value
A few years ago, some Atlassian developer changed "Blame" in the BitBucket UI to "Annotate". I remember a lot of people being frustrated because they couldn't find "blame" anywhere and the change was never officially announced. It just happened one day
Someone opened a ticket with BitBucket about it which ended up drawing a lot of attention from frustrated users who couldn't find "blame", and their searches for it on Google led people to the ticket. Atlassian eventually responded saying that they made the change because "blame" sounds bad and can hurt people's feelings somehow (with no examples given of course, though ironically the dev who made the change certainly had hurt feelings after the upset masses had some choice words for the short-sighted decision. Though Atlassian doubled down and I believe closed the ticket without reverting the change, so the confusion remains, as far as I know)
I don't think that they ever mentioned the Subversion/CVS parallel that was drawn to choose that name, so it was really confusing why that was selected. But this comment shed some light on that ancient incident
Digital piracy has been around for decades, naturally. The primary thing that computers do is copy data (you download a book, that's a copy on your hard drive. You read it, you've now copied it to RAM and to your graphical display. You sync it to another device, that's another several copies, etc). It will never be stopped