Repple (she/her)
- 0 Posts
- 210 Comments
1·13 days agoHonestly the 2008 real estate/subprime bubble felt the same way. People were talking about the bubble popping for what seemed like forever until it actually did.
I believe that one was Beast Wars
Fuck I need to do something like this. I’m terrified of the loss of income though. I need to make my life cost less.
Well, if you consider programming an art, it’s fucking destroying art.
1·1 month agoUhhh splatoon raiders and Imagine Me and You (a lesbian romcom)… Lena Heady grabs a Squiffer and starts taking out hordes of salmonids? Yeah, I’d watch it.
Or maybe a lesbian romcom between agent 3 and the mechanic in London. Also pretty fantastic.
This AI work is normally not classified as “GenAI” which is what I was responding to, and the parent was specifically talking about LLMs. Usually GenAI specifically refers to LLMs as well as image/video creation.
The big data centers aren’t for the most part being built for pharma research.
6·1 month agoI hate to say it but I think I have to now: I don’t like Strange New Worlds. I loved lower decks and SNW started out with a ton of promise (and some eps I do really genuinely enjoy) but with so few episodes and of those so few feeling like Star Trek exploration, I just think its not for me. A shame cuz I love the cast and the design.
Super happy others still enjoy it though.
This to me seems to be a very odd interpretation of the phrase “coding was never the hard part”. First, that doesn’t mean that it’s not hard, just not the hardest. Second, and more importantly, they jump to deciding what to build being the hard part as if those are the only two things?
I have used a variation of this phrase (I usually say coding was never the bottleneck at work) but I’ve never even considered deciding what to build as to be what the bottleneck is.
First, I should say by coding I mean taking a concrete design for a change and writing a single pass at implementation. Modern models to this extremely quickly with up to good performance depending on exactly what you ask them to do.
The things that take up more time in software development just for engineers, leaving aside things that design and pms do.
- Coming up with that concrete design for a change (humans may do this in many ways, one of which is writing the code without a plan and refining)
- Architecting the system at all levels. This one is continuous and huge. A good architecture will easily adopt changes as they come, but you can never foresee all possibilities, and even if you could, there’s usually other people around you who can’t, which brings me to
- Communicating the system design and coming to consensus about aspects of it. This is mostly applicable to teams and is the primary reason individuals can often outperform entire teams. It’s also one reason why throwing a second LLMs at a problem doesn’t solve it at twice the rate. You’ll never get linear scaling
- Upkeep tasks: what needs to be replaced and fixed now, how do we best monitor and alarm to figure this out in the future.
There are “what to build” aspects in here and many engineers also spend time on the overall what to build questions, but the way the article was talking about it seemed very high level.
Coding isn’t easy, it’s hard. But it’s also not usually the bottleneck in software development.
This to me seems to be a very odd interpretation of the phrase “coding was never the hard part”. First, that doesn’t mean that it’s not hard, just not the hardest. Second, and more importantly, they jump to deciding what to build being the hard part as if those are the only two things?
I have used a variation of this phrase (I usually say coding was never the bottleneck at work) but I’ve never even considered deciding what to build as to be what the bottleneck is.
First, I should say by coding I mean taking a concrete design for a change and writing a single pass at implementation. Modern models to this extremely quickly with up to good performance depending on exactly what you ask them to do.
The things that take up more time in software development just for engineers, leaving aside things that design and pms do.
- Coming up with that concrete design for a change (humans may do this in many ways, one of which is writing the code without a plan and refining)
- Architecting the system at all levels. This one is continuous and huge. A good architecture will easily adopt changes as they come, but you can never foresee all possibilities, and even if you could, there’s usually other people around you who can’t, which brings me to
- Communicating the system design and coming to consensus about aspects of it. This is mostly applicable to teams and is the primary reason individuals can often outperform entire teams. It’s also one reason why throwing a second LLMs at a problem doesn’t solve it at twice the rate. You’ll never get linear scaling
- Upkeep tasks: what needs to be replaced and fixed now, how do we best monitor and alarm to figure this out in the future.
There are “what to build” aspects in here and many engineers also spend time on the overall what to build questions, but the way the article was talking about it seemed very high level.
Coding isn’t easy, it’s hard. But it’s also not usually the bottleneck in software development.
The good place is entirely fantastic, but season 1 is pure perfection.
1·2 months agoI’ll grant you your point for convicted, but not rape. We’re not talking in a legal context. The form of sexual assault he was found liable for was very much rape by the standard definition, which is more the correct definition than the legal one.
5·2 months agoBeen a huge splatoon fan since wiiu and raiders is no different. Super addictive gameplay loop and great fun coop with my wife. Music isn’t as strong as the rest of the series, though. But that’s an insanely high bar
2·2 months agoI’m still angry about that one and I have no connection to Croatia. Completely robbed.
3·2 months agoWhen you think about these questions they make less and less sense. Like. Do your atoms shrink? If so air is too big to process and physics makes no sense as far as I understand it. If not, you’re just losing the vast majority of them and there’s no way human biology will continue to work at all…
I also look at and treat all non-human chordates the way other people deal with people
I was somewhat excited before this because I enjoy splatoon campaigns, but once they announced co-op I’m now all in.
I tried switching to ddg several times over the last decade or so and always gave up because of issues like this, especially with technical or obscure topics. Recently started paying for Kagi and do not have the same issues at all there. The results are good and nicely presented without ads. Of course, on the flip side it’s pretty expensive.
We really are.