Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
AlgoRythm4515373dSo yes, welcome. Your first question will be to debug this TOTALLY NOT CURRENTLY IN PRODUCTION code. It has a bug... somewhere... and it's really tough.
WorstVarNames9371d@dfox i am curious about the question end part. What do expected to hear?
Honestly in 5 years I dont think I failed at anything, i delivered what was planned otherwise i would be fired if i failed?? Dont know.
The only thing i would consider close to it, was at the first years i didnt know how to structure css along with components (angularjs) and made a total and not reusable mess 😅 but it kinda part of the process if u dont have anyone more experienced to teach u better
dfox4433070d@WorstVarNames good question. I think the relative size of the “failure” can be almost anything.
Ex. Over-promising, launching a feature that didn’t scale well, team conflict, missing something during planning stage, scope creep, cost, unexpected errors, building something that failed to address issues in a larger system it was meant to help, etc. so many things. I don’t think there’s any dev who hasn’t encountered some of these.