I can’t wait for hamster wheel version 12! So much more range than v1

somebody in the room will ask what the flight ceiling is

Sir, this is a Wendy’s

The real flaw in the diagram is that all the intermediate steps of Agile are usable products. All 5 of those are completed, sellable products. Agile pivots way before any of these become usable.

Usually signalling for help isn’t something you leave to day 2… I think they might just be taking a vacation.

I’ve actually noticed this exact thing with elevators before… I was kind of amazed the beep and light were hooked up completely independently from the actual floor selection logic.
It sort of makes sense that the light in the button would just be hooked directly up to the button contacts. The computer would then be polling the buttons separately and it’s possible to miss a button press… These sorts of buttons shouldn’t need a debounce period since pressing any of them a second time doesn’t do anything. If the buttons were interrupt based, this probably wouldn’t happen.

deleted by creator

Anything that’s per-commit is part of the “build” in my opinion.

But if you’re running a language server and have stuff like format-on-save enabled, it’s going to use a lot more power as you’re coding.

But like you said, text editing is a small part of the workflow, and looking up docs and browsing code should barely require any CPU, a phone can do it with fractions of a Watt, and a PC should be underclocking when the CPU is underused.

It sounds like it does save you a lot of time then. I haven’t had the same experience, but I did all my learning to program before LLMs.

Personally I think the amount of power saved here is negligible, but it would actually be an interesting study to see just how much it is. It may or may not offset the power usage of the LLM, depending on how many questions you end up asking and such.

I didn’t even say which direction it was misleading, it’s just not really a valid comparison to compare a single invocation of an LLM with an unrelated continuous task.

You’re comparing Volume of Water with Flow Rate. Or if this was power, you’d be comparing Energy (Joules or kWh) with Power (Watts)

Maybe comparing asking ChatGPT a question to doing a Google search (before their AI results) would actually make sense. I’d also dispute those “downloading a file” and other bandwidth related numbers. Network transfers are insanely optimized at this point.

Just writing code uses almost no energy. Your PC should be clocking down when you’re not doing anything. 1GHz is plenty for text editing.

Does ChatGPT (or whatever LLM you use) reduce the number of times you hit build? Because that’s where all the electricity goes.

Asking ChatGPT a question doesn’t take 1 hour like most of these… this is a very misleading graph

Or just std::bitset<8> for C++. Bit fields are neat though, it can store weird stuff like a 3 bit integer, packed next to booleans

It’s probably graded by a computer, and a) or d) is a fake answer, since the automated system doesn’t support multiple right answers.

I’m going to go with 25% chance if picking random, and a 50% chance if picking between a) and d).
If it’s graded by a human, the correct answer is f) + u)

Thanks for responding. I’m not really a web dev, so I haven’t thought about it much.

The tab layout and <div> examples were definitely not things I was thinking about. I guess that’s a good incentive to use tags like <section> and <article> instead of divs with CSS classes.

I’m actually a bit color blind myself, so I appreciate sites being high contrast and not relying on color alone for indicators. A surprising number of sites completely break when trying to zoom in and make text bigger too, which is often due to bad floating layouts. Especially if it’s resized with JS…

I’m curious what parts would be challenging to use with a screen reader? If a site just has basic links and no JS, I can’t really think of anything unless the tab layout is somehow completely shuffled due CSS.

This was all people were talking about when they bought GitHub. We’ve past the “Extend” stage now.

My opinion is that including trans people in this sort of study actually reduces the bias, because they’re the only people who will have experienced the social impacts of presenting both male and female at different times. All cis-gendered people will be inherently biased towards their own limited experience.

Most of those seem like nonlinear relationships, so it still doesn’t make any sense still. The undergrowth would only start becoming an issue when the height gets taller than the egg diameter.

For NASA, data types don’t matter when you’re programming Voyager 1 and 45 years later it gets hit by an energy burst causing 3% of the RAM to become unusable, and it’s transmitting gibberish. It’s awesome they were able to recover it.

This still isn’t specific enough to specify exactly what the computer will do. There are an infinite number of python programs that could print Hello World in the terminal.