I'm always fighting to get people to start thinking about areas of responsibility and consistency across codebases, since the natural tendency is to just add whatever functionality you think you need wherever you happen to be working at the time. I mostly work in C# but at least it has nullable annotations these days. I don't think null guards are really that bad though, at least when you have a language that lets you do it smoothly, like Kotlin and Typescript. Like the author said, it mostly gets real bad when you let responsibilities get all muddy.
No one would do that. On mine it's a switch but most are wired to the brakes as you mentioned. The main benefit is really just that you get brakes for free without any wear, though it is only generally possible on direct drive hub motors.
Not sure I agree with the "three pillar" framing in this one. I think it's more like he was able to use the LLMs effectively because he had already built those years of experience. Someone new trying to vibe code their way into designing robust distributed systems is going to need a similar amount of time to build the correct intuitions, because the LLM doesn't give a shit one way or the other, it'll just do what's in the prompt.
On the other hand, commodotizing domains that fit a repeatable pattern isn't so bad, is it? At work I sometimes have to remind people that we're generally just building CRUD apps to interact with data, which isn't exactly at the bleeding edge of software. I like the idea of software engineers getting to be more portable, but unfortunately the industry still thinks LLMs are going to replace most jobs, which is obviously not possible.
It's probably one of those ironic names, but Psychedelic Porn Crumpets always makes me die a little when I'm trying to tell people about 'em. Great band, dumb name.
Rush. Love the 70s and 80s eras especially, but it's like having several favorite bands to choose from! If I'm in the mood for synths I'll put on Signals, or if I want something heavier I'll play the self-titled album. I literally never get sick of their songs though.
I think we're coming to the end of a 50 year cycle of rapid technological improvement that's been a parasitic host for capitalistic predilections. Shareholders ride tech companies hard and put them away wet, fucking over workers and squeezing consumers in the process. Innovative and awesome companies end up getting subsumed into a shit whirlpool where the product gets worse, more expensive, and steals your data. So I guess the people in my example are the tech investors and MBAs feeding them, and their abuse of tech is what needs to die.
A proper type system should be like the bumpers in a bowling alley, where you know the ball will at least stay on the track. Typescript is more like the ball launching ramp, where you probably won't yeet the ball straight into the gutter but it can still certainly end up there.
I agree TS is just not a good idea to start with, but it might at least be respectable if it actually had runtime enforcement. Maybe then node wouldn't be as horrible, though you're always better off with a real backend language anyhow.
I'm also a software engineer who doesn't care about most new tech. I strongly believe that human made objects and software can both reach a state of doneness. For example, books are a technology that's "done". Both physical and digital books do a great job at delivering written content, so there's no need to keep buying the same damn thing every couple years. Phones are similar, yet the new ones just get shittier (no removable battery, no headphone jack). Kind of reminds me of how Microsoft keeps trying to solve the "problem" of programmers being needed to create programs. Powerapps being one of the latest examples.
Based on things I've seen I can actually believe this is real. Just goes to show that you can't trust everyone to have a functional intuition for separating horrible ideas from good ones.
Funny thing about Powershell is that it was controversial inside of MS when it was first created, and the inventor had to really push for it to make it into Windows. Everyone thought people wanted wizards for everything instead. There's a great Corecursive episode about it. https://corecursive.com/building-powershell-with-jeffrey-snover/
I use it as a search engine but not as my only source. It's really good at regurgitating the most relevant Stack Overflow answer I might find, which may or may not actually be applicable to my situation. As a rule I never copy paste code directly, I always rewrite it "in my own words", even in cases where it's basically the same. If the code it provides is more than 5 lines or so I can almost always think of a better way. I feel like I'd still be better off with a really solid reference manual though, and a recipe book. But they go out of date too fast these days.
I'm always fighting to get people to start thinking about areas of responsibility and consistency across codebases, since the natural tendency is to just add whatever functionality you think you need wherever you happen to be working at the time. I mostly work in C# but at least it has nullable annotations these days. I don't think null guards are really that bad though, at least when you have a language that lets you do it smoothly, like Kotlin and Typescript. Like the author said, it mostly gets real bad when you let responsibilities get all muddy.
No one would do that. On mine it's a switch but most are wired to the brakes as you mentioned. The main benefit is really just that you get brakes for free without any wear, though it is only generally possible on direct drive hub motors.
Not sure I agree with the "three pillar" framing in this one. I think it's more like he was able to use the LLMs effectively because he had already built those years of experience. Someone new trying to vibe code their way into designing robust distributed systems is going to need a similar amount of time to build the correct intuitions, because the LLM doesn't give a shit one way or the other, it'll just do what's in the prompt.
On the other hand, commodotizing domains that fit a repeatable pattern isn't so bad, is it? At work I sometimes have to remind people that we're generally just building CRUD apps to interact with data, which isn't exactly at the bleeding edge of software. I like the idea of software engineers getting to be more portable, but unfortunately the industry still thinks LLMs are going to replace most jobs, which is obviously not possible.
Definitely some major similarities, but HoL has a lot more depth (no pun intended).
I went on that ride, I do remember there being pyrotechnics! It wasn't unpleasant though, just thrilling for my 9 year old self.
Not when you read Peter Hamilton and Alastair Reynolds lol.
It's probably one of those ironic names, but Psychedelic Porn Crumpets always makes me die a little when I'm trying to tell people about 'em. Great band, dumb name.
No way, I loved that show. It was great but flew under the radar.
Why not use python at that point? Sounds like the bus factor would be pretty big on this one
That's odd, I can do either of those things independently. Maybe it's just wired that way for some people?
Rush. Love the 70s and 80s eras especially, but it's like having several favorite bands to choose from! If I'm in the mood for synths I'll put on Signals, or if I want something heavier I'll play the self-titled album. I literally never get sick of their songs though.
I wasn't too much of a fan till I saw them live (twice!) and they actually slay. Great band!
I think we're coming to the end of a 50 year cycle of rapid technological improvement that's been a parasitic host for capitalistic predilections. Shareholders ride tech companies hard and put them away wet, fucking over workers and squeezing consumers in the process. Innovative and awesome companies end up getting subsumed into a shit whirlpool where the product gets worse, more expensive, and steals your data. So I guess the people in my example are the tech investors and MBAs feeding them, and their abuse of tech is what needs to die.
I don't even need something as cool as this, but can we please start prioritizing non laggy UIs again!?
A proper type system should be like the bumpers in a bowling alley, where you know the ball will at least stay on the track. Typescript is more like the ball launching ramp, where you probably won't yeet the ball straight into the gutter but it can still certainly end up there.
I agree TS is just not a good idea to start with, but it might at least be respectable if it actually had runtime enforcement. Maybe then node wouldn't be as horrible, though you're always better off with a real backend language anyhow.
https://youtu.be/FuwIM2m-4yY
I'm also a software engineer who doesn't care about most new tech. I strongly believe that human made objects and software can both reach a state of doneness. For example, books are a technology that's "done". Both physical and digital books do a great job at delivering written content, so there's no need to keep buying the same damn thing every couple years. Phones are similar, yet the new ones just get shittier (no removable battery, no headphone jack). Kind of reminds me of how Microsoft keeps trying to solve the "problem" of programmers being needed to create programs. Powerapps being one of the latest examples.
Based on things I've seen I can actually believe this is real. Just goes to show that you can't trust everyone to have a functional intuition for separating horrible ideas from good ones.
Funny thing about Powershell is that it was controversial inside of MS when it was first created, and the inventor had to really push for it to make it into Windows. Everyone thought people wanted wizards for everything instead. There's a great Corecursive episode about it. https://corecursive.com/building-powershell-with-jeffrey-snover/
I use it as a search engine but not as my only source. It's really good at regurgitating the most relevant Stack Overflow answer I might find, which may or may not actually be applicable to my situation. As a rule I never copy paste code directly, I always rewrite it "in my own words", even in cases where it's basically the same. If the code it provides is more than 5 lines or so I can almost always think of a better way. I feel like I'd still be better off with a really solid reference manual though, and a recipe book. But they go out of date too fast these days.