[HashHishBang]

People like you are the reason people like me are QA/SETs. Your velocity, in my view, is some slapdash worked-15-hour-days-because-they-thought-they-could nonsense that is more likely to crumble under load and/or the first edge case that pops to mind. The only one capping their capabilities here is you mate.

[bitL]

You are naive. Did you work at world class companies that dominate their own market? They are exactly like that in the areas they are making money - they get the fastest programmers that could deliver world-class code. Not your typical half-baked developer quickly churning low-quality code in JS that breaks down after 5 seconds of load you get headaches from as a QA.

[HashHishBang]

>You are naive. Did you work at world class companies that dominate their own market?

Seeing as I'm currently sitting in my office at Adobe I would say yes. There are plenty of code jockeys like you churning out low-quality Java/Python/PHP/C/C#/JS/whatever. You, despite what you may think, are not special.

> Not your typical half-baked developer quickly churning low-quality code in JS that breaks down after 5 seconds of load you get headaches from as a QA.

Cute. I get headaches from the guys who think they're great. From the ones who think that not documenting what they do is time wasted because clearly what this does is obvious. I get headaches from the people who have NO IDEA how their code actually performs and if there's any kind of slowdown well just throw more money at the hardware.

I can practically hear you and the others like you cry out, "But it works on my machine!" Oh the headaches that has caused.

[bitL]

> There are plenty of code jockeys like you churning out low-quality Java/Python/PHP/C/C#/JS/whatever.

OK, I landed #1 spot on HackerNews with a product I mostly developed (under a different nick) some time ago. You know everything about me as well. It was also competitor of one of your products.

All I am saying is that these are assumptions/metrics with which VCs/owners run/structure their companies and what actually matters to them. I have experienced it dozen times. I have also experienced when I had to fix somebody's horrible code in production developed in high velocity/high stress/low quality mode that was bringing one famous tech company down (lawsuits etc.), and had to correct spots I'd never seen before in some of the most complicated areas of the product dealing with provably infeasible problems (distributed systems). I'd also experienced an environment in a relaxed top company (rated higher than either of FAANGs) where we discussed ad infinitum just individual names of functions, their parameters and if they perfectly capture their meaning and refactored them daily; I don't have to say that project wasn't having much of a velocity and its market share reflected that.