• 1 Post
  • 45 Comments
Joined 2 years ago
cake
Cake day: July 26th, 2023

help-circle
  • The idea is to have water or molten salt cool the walls of the torus from outside, and those drive ordinary turbines like any other generator. The main issue is that particles fly out of the confined plasma donut and degrade the walls, whose dust flys into the plasma and reduces the fusion efficiency. They’re focusing on the hard part - dealing with the health of plasma sustainment and the durability of the confinement walls over time. Hot thing that stays hot can boil water or salt to drive regular turbines, that’s not the main engineering challenge. I get your frustration where it feels from news coverage that they’re not focusing on the right stuff, but what you’ll likely eventually see is that the time between “we figured out how to durably confine a healthy plasma” will quickly turn into “we have a huge energy output” much like inventors puttered around with flight for hundreds of years until a sustained powered flight design, however crappy, finally worked. From that point, it was only 15 years until the first transatlantic flight.










  • I think the size may have more to do with the team not splitting up the Unreal build paks. Haven’t checked how well it’s actually split up, but I can say that changing even one small thing could result in a giant update if that build has like one pak file with all the things in it. There are ways to configure it in the build but it’s not a magic toggle either. Worked with a studio handing off UE builds before that didn’t build the game in a split friendly way and it made every upload to S3 take forever cause there were only like two really giant paks.

    Also makes me wonder, does Steam not do diff patch style updates for changes within individual files? If not, that could save a ton of bandwidth.









  • Yeah management is totally backwards there; it’s like the building manager on a construction project going “all electrical needs to be done in X weeks”, but realistically they have no direct control over that deadline being met by declaring an arbitrary deadline. The unfortunate difference is that if you do a shitty job wiring a building, you’ll fail inspection and have to spend more time and money fixing it. Software can often hobble along; there aren’t strict enforcements for quality that the business can legally ignore, so you’ll always have sad defeated devs go “okay boss, we’ll skip the things we need to get this done faster for you (I hate this job and don’t care about the product’s long term success)”. Having a steady supply of those people will slowly kill a software company.

    In the past, I’ve dealt with estimate pushback not by explaining what necessary work can be removed like tests, documentation, or refactoring, but by talking through ways to divide the project more effectively to get more people involved (up to a point, a la mythical man month). That seems to go more proactively. Then we look at nixing optional requirements. But, I’ve also usually dealt with mostly competent engineering management.


  • The thing that frustrates me about developers who feel powerless over technical debt is…who is actually stopping them from dealing with it? They way I see it, as a software engineer, your customer is sales/marketing/product/etc. They don’t care about the details or maintenance, they just want the thing. And that’s okay. But you have to include the cost of managing technical debt into the line items the customer wants. That is, estimate based on doing the right things, not taking shortcuts. Your customer isn’t reading your commits. If they were, they wouldn’t need you.

    It would be bizarre if your quote for getting your house siding redone included line items for changing the oil on the work truck, organizing the shop, or training new crew members. But those costs of business are already factored into what you pay at the end of the day.