I get sort of paranoid over how well to model a problem. Too much focus on getting the "modeling" right could result in severe over-analysis and the possibility that nothing is shipped. Too little focus could result in an uphill battle forever thereafter.
For me at the moment it's lost context. An example is someone who made a decision to write code a certain way, or introduce a conditional statement, or something like that that is hard to figure out afterwards if undocumented either as a code comment or elsewhere
Hi, I normally contract in MSBI, SQL, Data Arcitecture, Oracle, .Net/.Net Core, API development, React, focusing on www.cryptostatto.com at the moment. Reach out if you see any synergy.
Projects with too much money. They never deliver value. You join them, everybody is best pals on good rates - then, when the crunch happens, the team moves into self-preservation mode.
Top comments (11)
For me it's getting out of touch with new things as I work in my domain of expertise. Big reason I hang around DEV.
I get sort of paranoid over how well to model a problem. Too much focus on getting the "modeling" right could result in severe over-analysis and the possibility that nothing is shipped. Too little focus could result in an uphill battle forever thereafter.
That my code isn't job worthy or worth sharing
For me at the moment it's lost context. An example is someone who made a decision to write code a certain way, or introduce a conditional statement, or something like that that is hard to figure out afterwards if undocumented either as a code comment or elsewhere
+1.
People misinterpret clean-code and think all comments are bad.
Comments that tell "why" are almost always helpful!
Phone and video call.
Projects with too much money. They never deliver value. You join them, everybody is best pals on good rates - then, when the crunch happens, the team moves into self-preservation mode.
Infinite loops.
Supply chain attacks
Having uncommitted code for 2 days or more