For further actions, you may consider blocking this person and/or reporting abuse
For further actions, you may consider blocking this person and/or reporting abuse
Michael Tharrington -
Nik L. -
Paulo Henrique -
dev.to staff -
Oldest comments (50)
It's frustrating, but also gratifying with the right mindset: When you spend hours on a problem, and the solution is some stupid typo.
It's literally the worst. Like— I just ruined my day for a typo.
The gratifying part is that these are usually the times where I read a lot of documentation, reach a lot of source code, and generally level up as a developer. Without that appreciation and acknowledgment, it's only frustration. 🥲
Disagreements. My way is the right way and I don't really want to hear otherwise. 😂
I've dealt with that my fair share, I find it best to ask people "why is this way better"
The software development.
Endless meetings about nothing..
Talking about software development with people who are either stupid or stubborn or can't think outside the box of their corporate environment.
I'd say it's gotta be development effort estimation. In an Agile workflow, this would involve planning poker during sprint planning, where each member goes about assigning story points for various tasks. The results can be widely subjective. Here are some reasons in my experience:
Most activities in software development can be solved to a degree, but this one seems so subjective that it almost feels like rolling a dice. Other than just adding extra time to the estimate (which raises the question - how much time?) to account for contingencies, I don't know if there is any strategy for this. Would love to hear other's thoughts. 😃
I would shorten this reply to "Agile generally"
Haha, i guess with the planning poker activity you can certainly say it's generally Agile.
But, planning poker or not, estimates are still hard wouldn't you say? 😅
They're a waste of time, so I don't do them
Interesting! Is it because your workplace doesn't really need you to calculate estimates one way or another? Or perhaps they're flexible enough?
I just gave up doing them. Maybe the PO filled them in for me, who knows?
The happiest, most productive teams I've worked on we're ones where we were allowed to self organise, and not estimate
I worked in a setting where estimates were not essential to business. The founder came up with a system like the following for communicating what work was being done and raising awareness of blockers:
You get very detailed visibility about blockers, direction of tasks, and choice of approach. Tech leads can daily or weekly provide feedback and steer in a different direction if choice of tasks or milestones are not leading to delivered results that will continue to accomplish overall project goals. There is no estimation, but you can look back and see gantt charts or calenders of microtasks.
This is an interesting approach to work! Would love to know more on what was the business domain that you worked in, where estimates were not super essential.
The company was a mixture of custom scientific consulting (writing running long, expensive batch jobs), custom application development, and a long term SaaS product, still in development. The projects that I worked on were for custom application development, and our clients were very flexible about delivery dates.
We had four experienced engineers using this workflow on four solo projects and they each loved it. I especially liked the visuals that Asana produces once you enter the microtasks. We also did a weekly report to summarize our feelings on how the project was going.
I see! I think more companies should adopt this working style. From what I've seen, many of them just want you to keep grinding sprint after sprint, insisting on deadlines even when there isn't any actual pressure from clients to ship a certain feature.
It actually is agnostic about how hard you work. For example, I put a lot of pressure on myself in that system to deliver a lot each day. I just like that it focuses on recording as you go and looking back, rather than spending lots of time on estimation, velocity, etc, and excessive time specifying tasks so that you can estimate them. I like deep requirements gathering though. I just don't like an obsession with estimation. My ideal system is something between the described system and kanban with bi-weekly retros.
The worst job that I ever worked (worked for about 10 different development shops), at a "best employer in healthcare" and "best employer in region", shoved this top down quarterly planning process on all the developer teams and had us spend 15% of our time in backlog grooming, task creation, scrum ceremonies, etc. Mostly well meaning people, just horrible experience for developers, no ability to focus or reach flow, task creation and grooming was a constant nightmare.
After that experience, I shudder whenever I see a tech company that has won "best employer" awards. I also don't trust Glassdoor anymore. I think the only way to learn about these problems is to experience a company first hand for a few weeks.
Also, if I see someone is using Jira, I start to ask very probing questions in interviews to try to understand why they arrived at heavyweight, clumsy jira.
Estimation is definitely a challenge that requires a team effort to get right. I recently shared a guide that I wrote for my own teams, perhaps there are insights that can help? A Guide to Story Point Estimation
Yes, this is one of the problems why I left a company.
this cannot be the reason why would you leave a company. perhaps suggest a process that would work with you or the entire team?
Explain development estimation to sudo technical manager is frustrating.
One extreme way to solve this is to go with #noestimates but it's a highly polemic subject. Some people (mostly managers ?) really love estimating things beforehand.
When I want to code, and I'm stuck on problems with my tech.
Yesterday I spent an hour solving wrong DNS setting in Ubuntu as I was cut from my remote repository, instead of finishing feature.
Finally solving this, my battery died out without warning.
Then I couldn't continue working in a bus as my ntb charging got stuck on 4%.
Requirement change after completing 90% task 😂
this needs to be higher. my most recent job has been actually pretty good about this though telling the business that they have to deal with it until a new story can be brought in an completed in the next sprint
Non-technical managers
Configuring AWS IAM policies lol
Reality.
You have a nice idea, and then you checkout what the market offers to help, and it's either legacy solutions or not yet production ready.
Software development is all about making compromises. The smarter you are, the better the compromise is.
Should you go all in on AWS because their CDK supports all their services? This means you have to use something like DynamoDB, which is rather low-level for a DB, or a relational alternative that isn't billed on demand.
Want to use something more modern, like FaunaDB? Well, then good luck finding a IaC framework that supports it and doesn't kill your vibes with YAML.
Reality usually sucks.
Javascript…just kidding.
I think the most frustrating is that software is highly susceptible to entropy. Which means guard strongly against dependencies. And be very wary of what all of those bells and whistles; much like the physical world, moving parts are more prone to breakage.
Dependency hell, annoying in a lot of programming stacks, but especially in NodeJS where you have to choose between being fully patched and secure vs. having a working app :(
Usually we have to accept that we can't patch a handful of vulnerable dependencies.
Unrealistic expectations. Often those expectations come from the outside, but they can of course also originate from the inside.
Sometimes I think "oh I did this in the past already, this should be easy".
If the task then takes longer than expected it feels very frustrating.
Handling those expectations properly is not always trivial in my opinion.
Communication