This will make it my default choice the next time I need to build a web app or service.
945 karma · joined November 8, 2008
This will make it my default choice the next time I need to build a web app or service.
Basically no user would do this but it's not somehow magically forced on the user.
Without a drastic overhaul across the entire industry around the definition of service providers "interface" and requirements around documentation, it'll just open an exciting new can of worms and pain for customers. Support will be hell, experiences that work seamless will be difficult to achieve.
Again - that's not to say it's a bad idea, it just seems like we'd need a real rethinking of how we're doing things as an industry. That could be good, or we end up with a tragedy of the commons.
First amendment protections should only apply to individuals anyway. Tesla doesn’t have a sane argument here since Tesla is not a person.
(I recognize there’s a whole bag of worms around corporations and attempts to treat them like individuals in the eyes of the law.)
That said - if my assertion is true, the Tacoma is truly a wonder with its reliability and so on. No surprise given it is the mobility platform of choice in Mid-East and Africa for militias and local armies (i.e. Toyota Hilux).
We still own one - a GLC300 from its first model year (2017) and it's basically been perfect. Zero problems beyond some cosmetic stuff w/ a seat rip but that's wear and tear. I care more about mechanical.
On the other hand, the E-class sedan we owned was nothing but trouble. I remember looking at some of the reported reliability data and it seemed like every 3-4 years, you'd have this cycle where the first year had great reliability and then it degraded over the next 2-3 years. When they released a new trim, reliability was back up.
Note - this is heavily anecdata, but having talked w/ other folks that owned multiple MB's, they felt it was similar.
My theory is it has something to do with the models manufactured in Germany versus the ones eventually offshore. Something doesn't translate as they offshore manufacture.
Rarely updated. Usually a conversational/expository style explaining what I did to fix something at home.
Its purpose is 99% to be a record of things I built/configured/did to remind me later. I write in a style I don’t find boring (e.g. not lab notebook style).
Sometimes people find it useful. ¯\_(ツ)_/¯
It's going to be a shit show.
The article reads like satire. I can’t tell if he’s making fun of the hoops you have to jump through to make a “modern web app”.
Either way, sketchy devs are capitalizing on the “gold rush” of generative AI.
I'm sure Amazon's offering will get better, but I don't really see much reason to move for now.
> (roughly) Japan is a country for the Japanese. While they may welcome you and invite you to experience their country and culture, the country is very much setup to serve the Japanese populace.
Apple feels similarly. They build what they need and enough to capture the revenue they want, but I don’t perceive them to really cater to external needs beyond what will monetize.
It sounds weird but you’d be surprised how often teams have lost any good reason to be doing what they’re doing at a micro level. They might still be on track at a macro level, they’ve just got pointless work slowing them up.
I've worked with both Azure and AWS professionally and both have had their fair share of "too many outages" or capacity issues. At this point, you basically must go multi-region to ensure capacity and even better if you can go multi-cloud.
I just can’t fathom Google’s inability to sort this out. They’ve been the laughing stock of serious cloud business for years.
That’s not people’s fault to make the comparison. Mastodon and the larger community does little to disambiguate this and make it clear.
(I say this as someone that’s used both Twitter and mastodon for years. They’re just different, period.)
Work doesn’t happen in Slack.
Something I started doing with $JOB-1 was to write a “Working with rufius” document and share it with the broader org (in slack profile or intranet profile). One of the things I provide is an SLA on responding to communication. It roughly looks like:
- phone call - synchronous
- email - if I am directly on to-line, response by end of next business day
- slack/teams - hours to never
I basically only answer slack if I’m paying attention to it for whatever reason. My typical work schedule has me open it 3 times a day - once in the morning, once after lunch, and once about 30 mins before I end my work day.
The other thing I note is I don’t make decisions in slack. Decisions happen in documents or worst case, email. Something durable.
That “Working with” doc has done wonders for setting expectations with coworkers. I’ve gotten a lot of feedback from coworkers as well that they appreciate it and have created their own.
They should have liquidated those holdings and put them in something safer.
Also - I question their characterization of how carefree these folks were. Of the few folks in my network that we knew rested and vested, many were so burnt out they eventually left the industry all together.
Edit: I wonder if they were smart and got out of their equity and into something better diversified. At least for a couple, my gut says no.
Good riddance.
I think there's something lost with not having junior engineers in office with senior and staff+ engineers.
I’m not hard line on “no interrupting”, but if I ask someone to stop, then I expect them to stop. Or I’ll just leave. I have other things I could be doing.
Microsoft is pretty rare for me to see in spam.