I also write a lot of python code. Ported 2 companies from python 2 to 3 too (idk why that keeps happening to me).
Lots of modern (...3+) python code uses type hints and a type checker. It can be as strict as you'd like it to be, which is exactly how I like it. It's what pulled me away from ruby.
Meanwhile, static languages are too often a giant pain in the ass, and in return for writing a lot of annoying code, you get in return guarantees that only really apply within your process's memory. And in a microservices world... you're actually realistically using the protobuf type system. Which generates just fine for python. And then "internally" you can use python's type checking where it helps, and if it doesn't help, then for that bit of the code, simply don't use it (and write "true" python).
I also find that a HUGE problem in the world is that programmers just. can't. help. themselves. They LOVE to over-define. LOVE IT. It's a siren's song!! Static type systems are a trap for the part of our brain that loves to architect. One of my favorite things about python is that it helps programmers _let go_. Not everything needs to be an interface. It's python. Everything is already an interface. Now just write the code without all the distracting 20 layers of indirection. And if we ever need one more, it's python - it's practically already there. Just make a new type, put @property on some methods, and you're good.
Obviously there are times I'd not use python. I could foresee myself writing Rust if I had to do code where correctness was of utmost importance (like, crypto, or embedded software for a medical device where someone's ventilator is hooked up to it, or similar). But if nobody's going to die (so... medical and cryptography...) then I'm using python almost no matter what I'm doing. And I'll use numpy or write a C module if I actually end up needing true CPU-bound performance for something.
Nah man that's how you end up in the permanent underclass. If you want to make it you have to throw everyone and everything else under the bus, be a bizarrely mustache-twirling evil misanthrope and general freakazoid-type loser, and most importantly get too big to fail / too rich to sue bc you have the good lawyers who can basically stall suits to death. Here's an application to Wendy's.
Sure, naturally. And yet parent commenter is remarking that simultaneously no AI-true-believer startups have supplanted the old money, and simultaneously despite much talk the bigcos have not slashed headcount to tiny AI-powered teams.
I've said this before: if anthropic (et al) thought they genuinely had a shot at replacing even 30% of white collar work, they would ABSOLUTELY NOT warn ANYONE. They would do what oil, leaded gas, and cigarette companies did. Swear under oath this is completely safe, commit GRIEVOUS societal harm that you explicitly promised wouldn't happen, and then end up in history books instead of jail for reasons beyond my ability to fathom.
No. The very fact they are trying to "warn" us means it's all marketing.
This has been corroborated for me on the engineering front that I can't find a single IC I respect who actually thought there was any evidence AI was going to live up to the hype. I saw a lot of people I always thought were idiots/sycophants/brown nosers go insane with AI. Never saw anyone id trust to help me cross a street blindfolded say more that "I may be wrong, but I'm not seeing any evidence yet".
It's not one or the other, it's both. Sqlalchemy ORM is my favorite, followed sqlc (golang), because they are both there for you for your highs (select * from table order by created at) and your lows ([an inner join followed by 4 left joins with an aggregation function])
Yes and no. There's a distinct auction that runs and it is a distinct event and has its own rules. Eg 5 mins (idr exactly, it's been 6 years for me) before the opening cross you can no longer cancel auction orders, post-only. At the open, they run an opening match of all the auction orders, THEN normal trading begins.
No, you're right. It basically just passes the buck. But the general idea is that if your transaction succeeds, you KNOW that there is a durable record that some external thing needs to end up in a message bus. And then something else can sit there and spin retries until it happens. It gives you the opportunity for retrying getting it onto the message bus, out of band of the process that is trying to initiate the enqueue.
And the outbox pattern isn't bs - it DOES help a lot in practice. But exactly how much it _guarantees_ something happens is of course still quite limited. And yes as you note it's an At-least-once strategy.
I am quite curious too. I had heard that, despite arm vascular being very consistent among individuals, it does still vary. And I think for most vaccines I guess it doesn't matter if you hit something other than muscle. Maybe for the mRNA vaccines it does matter? I'm baselessly speculating though. Wish other person hadn't been so vague.
We managed to generate probably-correct code, which can then be probably-corrected recursively to get to something that runs (usually).
This made everyone scream and lose their minds saying that code is finished, people think they don't need a technical cofounder anymore, think they don't need engineers anymore, etc. Then they're, at varying speeds, finding out they're wrong.
It seems oddly circular to me that the _exact hubris_ non-engineers have long accused engineers of - and we have indeed been too often guilty of - they themselves turn out to be JUST as guilty of! Just like engineers thought all sales did was bother people, and all marketing did was send emails, and all support did was tell people to turn it off and on again, and all product did was copy google... they all apparently thought all engineers did was tik-tak-click-clack type code all day and when it compiled it was done. Not knowing how much higher-order... well, engineering, there is to it.
Where are all the CTOs during all of this? I thought someone was supposed to be sticking up for their org? Sales, marketing, etc all seem to have entrenched C-suite people keeping their fiefdoms resistant to erosion by outsourcing, downsizing, etc. But all our CTOs seems to have collectively thrown us to the wolves.
Ok cool. Computers think. They're (trying to) use that to literally replace regular people. And not in a Star Trek way. "Permanent underclass" way. That's bad.
I would rather we not have technology than have people starving en masse. Literally our best hope is that the rich bastards are lying that they'll be able to do it to scam other rich bastards.
When I was in high school we were able to have an app that made it look like you were drinking beer. And the internet produced rainbow unicorn attack and nyan cat.
I was very optimistic about nyan cat. I'm very unoptimistic about nobody being able to afford computers for the next 5+ years.
Also since this thread is about general malaise - I am finding myself rather missing GW Bush's jovial brand of imperialism and cronyism. Strange fate.
The site is clearly libertarian, so they have a vested interest in trying to dunk on both the "left" and "right". When in actuality they're just lumpenproletariat who are going to get run over by the only people who have actual freedom in this country.
My oldest starting preschool was one of the worst times in my life. We were sick from august to december, then january to may. Dreadful.
It got better. My youngest is 3 now and is ahead of where my oldest was due to having 2 older siblings importing illnesses for several years, and this year we finally were mostly not sick all school year. Which is to say, we were probably closer to the 15 days "materially sick" mark. I say materially sick to mean, definitely sick, though perhaps not taken out of school (due to not technically being outside of the health exclusion policy, and sometimes I only realize they were "materially" sick after they got home instead of just "passably sick given kids will basically have a lingering cough from august to may).
Idk, I can imagine a specific weird usecase. I use IntelliJ. My coworkers don't. They don't want my .idea folder in git. (You're probably thinking "ok, yep, gitignore!" And you're right except my boss ideologically does not want any *hint* of what IDE you use in the repo. Including in the gitignore.
So each person putting .vscode or .idea in their local config's ignore actually makes sense. (Relative to the nonsensical parent requirement... of course).
People always point this out like it's some kind of gotcha. "But things were wrong before, too!"
But it wasn't ON PURPOSE. The INTENT, by the people serving the search, was for the information to be correct. Algorithms tried to reward correctness, people would curate information, etc. Sure, bad actors tried to game it. But since the intent was for it to be correct, search providers fought back.
With AI, you're literally intending for there to be this chance - and it's very hard to gauge what percent it is because it depends tremendously on your query - that the result is just straight up fucking wrong. Google search results didn't used to have a "btw this might just be totally madeup" disclaimer on them, or even on the quick-answer box.
The intent matters so much.
(I think this honestly extends to code too, though I won't belabor that point in this text box.)
I largely don't disagree with you but come to a different conclusion. I have two systems:
1) a "programming desktop" with a $500 upper mid range Ryzen (idr exact), 8GB VRAM Radeon card I bought solely for RuneScape, and 64GB ram
2) a maxed out Alienware 16 Area51, so it's a 5090 with 24GB vram and 64GB system ram. I bought it for gaming, of course.
I run qwen 3.6 35B A3B Q6 with 200k context window. I compare this to Claude pro max or whatever that I use at work.
The main difference between the machines is that the one with the RuneScape gpu does 10 TPS while the Alienware does 30-40tps. Both are fine though the 30-40tps is obviously a lot snappier.
I find with both models that:
- they do really well at "be a 30GB zip file of reddit and stackoverflow answers"
- they do really well at point fixing random bullshit errors that would otherwise waste my time (this is related to above of course)
- they do quite well at, given a pretty good specification of what you want, figuring it out, even if you've specified several steps needed
- they both cannot really be given a large ish task and left to just drive it on their own
The main difference between the two is with that last one, Claude is somewhat better and figuring SOMETHING out, but if Claude is having to figure it out, it's probably because I don't know what I want and it's very likely to not make a sane choice, and will generally produce slop given even the slightest amount of leash still.
I've also found that the boundary between "well specified small to medium thing" and "idk just do thing and figure it out" is the difference between you keeping control of the code and losing control. There's an "escape velocity" of AI use that, when you hit it, you're doomed to slop forever. (Or you have to deorbit... enjoy that). And while claude might have slightly higher velocity allowed while remaining suborbital, it's very diminishing returns.
So, are these models "worse" than Claude? Yeah. Am I looking forward to continued improvements? Yeah. But I now also have no desire to pay anthropic any amount of money, which has the nice side effect that i won't be helping them end up with so much money that they can distort our democracy.
No, if anything, I would say a very unfortunate trait of existence right now is that reality does NOT tend to punish corporations for being completely idiotic, at least not very fast at all.
Look at musk's companies. They will basically never (on any near timescale...) produce GAAP profitability and yet their IPO is in the trillions. To the point that S&P refusing to suspend their GAAP profitability requirements means the index will basically never see this company in it (which I'm quite pleased about).
The power of already-accumulated capital is simply more powerful than things like "don't be completely pants-on-head stupid about a recent fad" "don't seig-heil in front of the world stage" "there's no point in having people come to an office just to spend all day on zoom" etc etc etc.
The market can remain irrational longer than you can remain solvent, and companies can remain irrational longer than you can go without contributing to your 401k.
My sentiments too. I'm using Qwen 3.6 35B A3B on a machine with 64Gb ram and a 24GB 5090 (an Alienware 16 Area51 I bought, serendipitously, about 15 seconds before the idiots preordered all computers for the next 3 years and ruined everything).
You can't "slop cannon" vibe code with it, but this is personal code I want to not be spaghetti, so I'm not trying to vibe code. I just want to get instant retrieval of all stack overflow and reddit posts in a chat box, and for it to be able to spare me the physical pain of actually having to type out typescript code (I am a BE dev with negative patience for all frontend) and fuck around endlessly debugging obscure docker problems (I like docker, but, no patience for it having annoying problems and endless quirks). And this model does that really well.
Lots of modern (...3+) python code uses type hints and a type checker. It can be as strict as you'd like it to be, which is exactly how I like it. It's what pulled me away from ruby.
Meanwhile, static languages are too often a giant pain in the ass, and in return for writing a lot of annoying code, you get in return guarantees that only really apply within your process's memory. And in a microservices world... you're actually realistically using the protobuf type system. Which generates just fine for python. And then "internally" you can use python's type checking where it helps, and if it doesn't help, then for that bit of the code, simply don't use it (and write "true" python).
I also find that a HUGE problem in the world is that programmers just. can't. help. themselves. They LOVE to over-define. LOVE IT. It's a siren's song!! Static type systems are a trap for the part of our brain that loves to architect. One of my favorite things about python is that it helps programmers _let go_. Not everything needs to be an interface. It's python. Everything is already an interface. Now just write the code without all the distracting 20 layers of indirection. And if we ever need one more, it's python - it's practically already there. Just make a new type, put @property on some methods, and you're good.
Obviously there are times I'd not use python. I could foresee myself writing Rust if I had to do code where correctness was of utmost importance (like, crypto, or embedded software for a medical device where someone's ventilator is hooked up to it, or similar). But if nobody's going to die (so... medical and cryptography...) then I'm using python almost no matter what I'm doing. And I'll use numpy or write a C module if I actually end up needing true CPU-bound performance for something.