What's worse is I've seen coworkers go from being curious about issues to just checking out and doing their tasks like you mentioned. But this is to be expected out of a place like Amazon.
2 weeks ago
| 12
Alot of the times it is not the engineer's fault. Sometimes there are multiple fires to put out. You move from one to the next. You tag the current fix as "short term" and say you will do a long term fix later. The "later" never comes. Working in a small-mid sized startup where you are constantly battling issues and changing priorities leads to this
1 week ago
| 3
I'm a junior working on a mature app suite by myself, I make notes of stuff that I find weird and write down my thoughts on what could be underlying issues or if I am trying to cross reference a feature in one place and implement it in another and see a bunch of what I've determined might be trash code I'll leave it but again make note and mention it to my mentor if we don't have any urgent feature requests or bug fixes to resolve. Thats my reason for not pursuing a chain of bugs, I'd love to dig into it but I don't have the time typically because I have a list of other things I need to get done by EOD or my sprint. I make backlog tickets if its something significant enough, but otherwise I just side eye it, make a note, and move on.
1 week ago | 0
I was like that first. But no appreciation for my efforts. No clarity however much questions, I asked. Actually, I was meant to do what was given at first. And later, what is expected from me changes after a year. 😂😂 Now I am meant to be curious about all problems. But when I ask for what is on the business side, it's still the same. Now concentrate on this..not that. But how come someone just works on the system without even understanding why it was built? Who are all the stakeholders? Things of that sort. I miss working at startups.. either way, I am always stresse
2 weeks ago
| 12
If only they paid me great money. Why should I do great work for a run of the mill salary?
2 weeks ago
| 9
A Life Engineered
I watched so many people get stuck in the same pattern at work.
They'd fix the immediate problem, check it off their list, and move to the next task.
They never asked, "Why is this thing a problem in the first place? Can I prevent problems like this from occurring in the future?”
The difference between good problem solvers and great ones isn't skill.
It’s curiosity.
A good engineer fixes the memory leak. And then the next one. And then the next one.
A great engineer wonders how we can add safe-guards to prevent memory leaks from happening.
I share more insights like this with people in my Discord community. Join us for deeper conversations: discord.com/invite/HFVMbQgRJJ.
2 weeks ago | [YT] | 184