The week has just begun. A dozen more deadlines have probably been tossed at you already. So, let's detox a little today.
What's the one thing that really bugs the developer in you?
Vent out in the comments below. 💆♀️💆♂️
The week has just begun. A dozen more deadlines have probably been tossed at you already. So, let's detox a little today.
What's the one thing that really bugs the developer in you?
Vent out in the comments below. 💆♀️💆♂️
For further actions, you may consider blocking this person and/or reporting abuse
Oldest comments (76)
This sums it up accurately for most developers I guess:
I think this sums up why I don't mind being a QA :P
This sums up why I'm frightened of QAs 😅
This situation can mostly be solved by changing the design process. But - they'll always be things that don't work... and that's a mind-shift. TDD can help / and early prototypes of feature too. But - yeah... so many things to take into account!
What's the difference between a feature and a bug?
Isn't butterfly a bug?
You want the feature to be noticed.
I'm aware that it's part of the hustle... but my answer would be, having to make changes to something they swore was completely finished last week :'D
yh. i totally agree with you.. most annoying thing ever
This hurts.
Especially when you literally talked with them about that exact scenario, and let them confirm twice that that won't ever be needed.
I'll get a lot of hate for that but there are two things that irritates me the most :
Re 2: that's because you have the mindset of a dedicated developer. Which is of course good for a dev, however, on the business side
sometimesit's more important to deliver and make $$ then slowly solve issues (if you ever solve them) than make it perfect from the start.Personally I think the best solution is a compromise, don't 100% mess the code just for easy gains, but do find suitable shortcuts when possible (and yes, non-native apps can be suitable shortcuts in some cases)
Or you can use something like Ionic with Capacitor and get native plus web stack
First of all, I don't really hate you or your answer, but I'd like to transcend its sentiment.
Development is all about the compromises you make - and you will make them, consciously or not. For example, by adhering to a "use the right tools" workflow, you compromise on the ability to use tools you deem "wrong" to greater effect, which especially for prototyping can be a bad choice.
Which brings us to your second point: when we are aware of the compromises, we should also know the consequences and make them transparent. Using electron for an UI means that you trade consistency with the platform with consistency over platforms.
If you make this choice, it should be a conscious one - just like all of the other compromises you make all the time on a daily basis. However, that does not mean that you sacrifice app quality - and how much money you spend on what is not the choice of the developer, but of the manager. The developer's task here is to make the consequences of each choice transparent.
Human beings
My last two weeks have been stuck in an Office Space loop of "Did you get the memo?" I assure you I have the cover sheet on the TPS report just fine, tyvm.
There's a process for putting code in prod. All the people involved in the process were laid off. The new people in charge of the process are redoing the process docs. I've gotten at least 5 emails about the new process docs.
I had to make our docs 3 weeks ago so we could have time to get to prod. Apparently they updated the docs 2 weeks ago. I have gotten at least 3 comments about how I'm using the old template and didn't I see the emails about how to make a new doc from a template. Like, yes, I have. But these docs are based on the 3 weeks ago template so we had time to fill them out. But did you get the memo about the new process templates.
I already had a week of PTO on the books starting tomorrow, but now I need it.
Unnecessary meetings for the sake of meeting.
we are team of 6 developers, I face this issue alot :(
Just posted this on LinkedIn...
In response to the "intimacy" argument for Zoom:
I'm failing to [frozen video] how [glitchy stutter] [movement] [frozen again, with Aphex Twin sound stretch effect] [blank screen] intimacy.
Arrogant, know-it-all coworkers
Sounds like a problem with the boss!
Working on Legacy app (20 yrs old) 🥺
I always hate the "we've been doing that for years, we're not changing that"-attitude. Really crashes creativity and innovation.
true that!
Clients that think that they are important enough for a (interrupting) call. Unless a server is burning, send a mail, I’ll check when I have time.
5 projects in a day... context switching is killing.
Some comments may only be visible to logged-in visitors. Sign in to view all comments.