I mean, that's also exactly what you would say if you had a $150M offer on the table, had received a lot of push back and were now just checking the waters and waiting to consolidate your position.
I just had flash backs to a previous job where I was brought in to optimize another teams builds since they were now taking minutes instead of seconds.
I tracked it down to a folder with thousands of C++ files called things like uint_to_int.cc and inch_to_cm.cc and cm_to_m.cc. Basically the developer in charge of writing the conversion library took our typed units library and autogenerated a C++ file for every possible conversion the application might need to make.
Every time we added a new typed unit it would create another couple of dozen files to be compiled.
> There's an alternative: Android. I'm perfectly free to use that instead. I don't.
I think this is my entire problem with most of these conversations. When they say "The walled garden has to end." ... they mean "YOUR walled garden has to end.".
I also like the Walled Garden. Do I think Apple should be able to charge more than Stripe? No.
I wish they would stop conflating the gate keeping price to enter the walled garden being too high with the wall garden and the gate being a moral wrong.
Apparently, the market can bear Apple charging more than Stripe. Hell, Stripe's business model is just moneychanging at its core; at least Apple can make an argument that they do more than that.
A friend of mine works beside one of the Eglinton line sites and called me a few years ago to tell me they were taking down the hoardings... because the hoardings had rotted and needed new plywood and studs.
Yeah, something happened a few months ago where by iOS I'm now "hitting" the wrong key a lot, words like we'll and we're are constantly being automatically "corrected" to well and were and, most frustrating, it will auto"correct" the last word in a sentence from what is on the screen when you hit send. It went from almost always helpful to often frustrating.
Oh they TRY to ... it's just that the "non-technical unqualified people" get brought to heal (usually) by regulations. I've been in the room where people have tried to force a decision and a PEng, Lawyer, or CA/CPA had to say "absolutely not". It happens all the time, which is why you NEED regulations.
> We can build huge things like airliners, massive bridges and buildings without starting small.
We did start small with all of those things. We developed rigorous disciplines around engineering, architecture, material sciences. And people died along the way in the thousands[0][1]
People are still dying from those failures; The Boeing 737 MAX 9 crash was only two years ago.
> Incremental makes less sense to me when you want to go to mars.
This is yet another reason why a manned Mars mission will be exceedingly dangerous NOT a strike against incremental development and deployment.
All the sites that I'm personally aware of are either NOT behind Cloudflare, are large and targeted, or are behind Cloudflare because they have actually experienced a DDOS attack(s). I don't know of anyone that is just sticking themselves behind Cloudflare willy-nilly.
You can't. That's the use case FOR AWS/GCP. Once the differential between having a in-house team and the AWS premium becomes positive is when you make the switch.
A lot of the discussion here is that the cost of the in-house team is less than people think.
For instance: at a former gig, we used a service in the EU that handled weekends, holidays and night time issues and escalated to our team as needed. It was pretty cheap, approximately $10K monthly fee for availability and hourly rate when there were any issues to be resolved. There were a few mornings I had an email with a post-mortem report and an invoice for a hundred euros or so. We came pretty close to 5 9's uptime but we didn't have to worry about SLA's or anything.
There is also the factor that the idea that you don't need administrators for AWS is bullshit. Cool idea, bro. Go to your favorite jobs portal. Search for "devops" ... 1000s of jobs. I click on the first link.
Well, well, they have a whole team doing "devops administration" on AWS and require extra people. So not having the money for an in-house team ... no AWS for you.
I've worked for 2 large-ish firms in the past 3 years. One huge telco, one "medium" telco (still 100s of people). BOTH had a team just for AWS IAM administration. Only for that one thing, because that was company-wide (and was regularly demonstrated to be a single point of failure). And they had AWS administrator teams, yes teams, for every department (even HR had one, though in the medium telco all management had a shared team, but the networking and development departments still had their own AWS teams, who, btw, also did IAM. The company-wide IAM team maintained an AWS IAM and some solution they'd bought that also worked for their windows domain and ticketing system (I hate you IBM remedy), and eqiupment ordering portal and ...)
AND there were "devops" positions on every development team, and on the network engineering team, and even a small one for the building "technics" team.
Oh and they both had an internal cluster on top of AWS, part on-premise, part rented DC space, which did at least half the compute work (but presumably a lot less of the weird edge-cases), that one ran the company services that are just insane on AWS like any kind of video.
they sell "you don't need a team"... which is true om your prototype and mvp phase. and you know when you grow you will have an ops team and maybe move out.
but in the very long middle time... you will be supporting clients and sla etc, and will end up paying both aws AND an ops team without even realizing.
reply