4 ms·
The "we saw this problem at X place" always brothers me. I'm old, I could come up with endless such stories that would require epic solutions, but in not sure
by duxup 5y ago
The "we saw this problem at X place" always brothers me.
I'm old, I could come up with endless such stories that would require epic solutions, but in not sure there would be much gain. Tell me why we will hit that issue and why we can't fix it any other way... not just the vague notion of a problem someone else had for who knows what reason...
And the reason I want that level of detail is because I've failed to accurately predict such issues time and again too ;)
- pbourke 5y agoThere’s no one as dangerous as a new hire from “X,” where “X” is a well-known/esteemed company (FAANG, etc), in their first 3 months at a new firm.
- colechristensen 5y agoIt doesn’t even have to be somewhere notable, beware of the engineer trying to recreate their previous environment (and in yourself too).
- void_mint 5y agoIn my career I've found this to be a huge huge huge red flag as well. If you can only build software one way, you don't really understand how to build it. If moving to a new employer means replicating a previous employer's practices exactly, I don't think you really lack the knowledge or reflectiveness to understand what was good or bad about it.
- void_mint 5y ago* I don't think you really have the knowledge or reflectiveness to understand what was good or not Really wish I could just edit my comment.
- void_mint 5y agoAt my last job, my boss was very guilty of "At ____, we found x to always cause us problems", but he never really connected that "x" was a problem because of the context surrounding it, not inherently. We went through this really awful process of: Manager either demands or rejects an idea based on a totally different company -> I spend days/weeks proof of concepting/documenting/testing/validating for or against his mandate -> He says something like "oh, great!", and then continues to spread the mantra that x would never work for us because of previous experience. It was really tiring. Having to constantly document why a piece of technology for a startup in a totally different industry would yield totally different results than when he'd used it at a top 5 company with insane scale and a 500 person engineering team. Especially because most of his understanding was just overhearing people say certain things, so he just said them too, but didn't really know why.
- duxup 5y agoYeah it absolutely can be an endless process. Human imagination is endless. You can't 'try catch' for everything that has happened sometime, even more so when addressing it at a high level without detail / nuance. You easily can get nothing done.
- void_mint 5y ago> You easily can get nothing done. That's exactly what we did. A year spent conducting experiments to validate or invalidate positions based in dogma rather than building, iterating and adding value.