Repple (she/her)

They were wrong about me on that one, though it is a place I’ve shipped a good deal to.

I’ve said it before and I’ll say it again: the Corbomite Maneuver is the most Star Trek episode of Star Trek and it was somehow just the 3rd to be produced.

I grew up with it and as I age I identify with those generations more and more. When I was young I didn’t want to deal with people to get things done, and to a certain extent I still feel that way, but we’ve given up so much for those touches of convenience and so many times we made the simplest use cases easy while completely fucking over the less common ones.

For example, a couple times within the last few years I’ve needed to check into hotels early in the morning. This has traditionally been easy: book starting the night before, call the front desk, let them know and they make sure not to give the room away. Well, seems like now some hotel chains only direct calls to the call center and don’t have a pathway to reach the front desk anymore. I tried telling them and they said they let the front desk know, and both times the room was cancelled.

Big corporations have too much power and it’s too hard to avoid using them. I’m lucky enough to have enough money where I can afford to go out of my way to choose small businesses but most people are really limited in how much they can do this.

Fuck. how could I have forgotten the escape velocity series??

In no particular order

Chrono Trigger

Splatoon

Ocarina of Time

StarCraft Brood War

Dragon Age: Origins

Honorable mentions: Mario 3, mass effect (1 and/or 2), tales of graces, Diablo II, tetris

Perhaps from Spanish bozal, used in the slave trade

https://www.etymonline.com/word/bozo

I would actually expect it in response. We could get some good headlines out of this

We really are.

deleted by creator

Honestly 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.

Uhhh 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.

I 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.

I’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.

I’m still angry about that one and I have no connection to Croatia. Completely robbed.