250 karma · joined May 3, 2017
But I realized the more I understood, the more dependencies needed to be changed. While it's still doable, things started to break and I ended up learning way more about the project than what was required to finish the task. In the end, it took me longer to finish it.
The fact that most of my coworkers would write a hacky solution in a short time, it made me feel incompetent. Managers without a technical background don't look at code, they look at results. So how do you even do #1 when the "other devs" still work there and can get stuff done much quicker?
That hacky workaround you're talking about? Well, my task depends on it. The workaround too depends on another hack. With the amount of time I have to work on it, it's a no brainer.
Earlier in my career, I tried to fix them, but they started to break other "hacks" and down the rabbit hole I go. Sometimes it's just not worth it.
Having said that, I much prefer working with code that is very simple and redundant with a verbose API, than with a codebase that is overly refactored and abstracted.
Finding the balance of the two extremes would be my definition of an ideal pattern.
If you can vouch for a friend to that degree, they probably don’t need your help.
I simply offered a reasonable solution to revoke JWT tokens. Would I use them in a project? Probably not. Even so, if an attacker has compromised someone's session, it's probably too late.
This is why it usually takes some websites 30-60min to completely revoke your password. This may be a concern for highly secure apps, but for most apps I think this will suffice.
While the author has mentioned a lot of things that I never knew existed or even care about, I don’t understand why Apple should have to make these things obvious for people who would never use them.
Same with vim. Too many options. Poor UX. Eg. Why are there two way to scroll down? Just use ctrl-d which helps you retain the context of the code you’re navigating.
I find it extremely fascinating that some people actually have to look for a scroll bar or clipped content (spoon fed) in order to scroll down. Sometimes I don’t even know there is one unless I have to speed drag on a long page.
However, these things happen time to time and when you have a stubborn PO like that from the beginning, you should have started looking elsewhere way before as a lead role. I’ve never heard of situations where a manager takes the blame. It always falls to the engineers.