We’ve never had a QA because we are on a tight budget but our PM is acting as a gatekeeper before declaring something as done.
However, there were too many cases that things were delivered as “ready” when they were not. PR review was not enough as everyone were checking diffs from GitHub only.
I implemented an intermediate step where the responsible engineer must post a screenshot or a short video of the ticket before passing to the PM and that alone resolved a lot of issues before they materialized on customers screens, just because you must take the extra effort to work on a proof of work.
It’s not just the destination - there are infinite shades of caring too much about every single line of code (spaces! Tabs! Inline open curly braces! Next line) and caring about the final result without attention to what is running under the hood.
I know exactly what he means - and as I said it all depends on personal drivers/motivation etc etc. take doctors: some starts the profession to make money other to care about people. Both categories can live under the same roof in a hospital.
A friend of mine went through the same - he got an alert for bill over budget, he logged in and boom 107M$.
I was on the phone with him and we checked that he didn’t leak any APIs keys but no traffic at all. I even thought of a breach at a vendor he uses for some s3 stuff before I found this thread on HN.
I think it all depends on your personal driver: personally I rather see a product I built in whatever way used by ever growing number of people because they find it useful. It means that the time I spent working on that helped other people solving a problem (hopefully).
That’s why a was always keen on cutting some corners when and where necessary in order to think about the user first and the code beauty second.
Of course I appreciate well structured and maintainable code but you can always strike a balance, even with LLMs assisted coding sessions.
How? If anything it seems like they are accelerating some processes - not least the export control over Fable just few days ago or the erratic behavior with the war with Iran
As an European, I really don't get where this strategy wants to take the USA to. It's pretty clear everyone is getting scared about changes like this that happen overnight, without clear reason and completely unpredictable.
Business requires a stable environment, and Trump is making everything in his power to disrupt business stability. Ultimately, I see the rest of the world (especially Europe) relying less and less on US tech. The long term damage is done.
All the US companies that used to think about the entire world (minus China) as their market will figure out that it is much smaller then they used to think.
Take Tally (tally.so), the one I took the time to check.
In their footer they say: Made and hosted in the EU which technically it's not wrong, but since they are using Google Cloud and Cloudflare, they are not insulated from the effect of the CLOUD Act.
Either way, one of the most critical parts is that many are still hosting on Google Cloud, AWS or Microsoft, therefore you are not 100% insulated from Cloud Act.
This is reminding me when Chrome and Firefox where racing to release a new “major version” (at least from the semver POV) without adding significantly new functionality at a time that browsers were already becoming a commodity. As much as we don’t care anymore for a new chrome or Firefox version so will be the release of a new model version.
However, there were too many cases that things were delivered as “ready” when they were not. PR review was not enough as everyone were checking diffs from GitHub only.
I implemented an intermediate step where the responsible engineer must post a screenshot or a short video of the ticket before passing to the PM and that alone resolved a lot of issues before they materialized on customers screens, just because you must take the extra effort to work on a proof of work.