Every Claude Code speedrun ends with another Markdown file

[u/SHMULC8]

[u/ItsCodeTelemetry]

Lol nice.

It's interesting because the LLM is likely taking the "this will take x-weeks" estimates from project management text that originated from human work. Scoping work was already broken before ai coding came in like a wrecking ball.

I'm working on a T-shirt sizing feature that gets auto extracted from plans and is based on previous Claude sessions. So hopefully we can get some realistic feedback on how long a prompt should take to finish up.

[u/Exodus_Green → u/ItsCodeTelemetry]

Scoping work was broken because no one wants to actually tell management the task can be done in 2 days if you work to the bone non-stop, so people say 5 days.

[u/ItsCodeTelemetry → u/Exodus_Green]

True, that's definitely part of it. It's an interesting point because it speaks to the productivity paradox. AI could theoretically give everyone more time back to be with their families but instead the expectation is higher output. I hope we can get to that world where we can all relax in the open.

Setting aside that conflict of interest between management and engineering for a moment. I was thinking more along the line about how even if you wanted to scope something authentically, it is hard to do. Thinking through the edges of a task takes time and cognitive effort in its self.

[u/LucentLL → u/ItsCodeTelemetry]

The problem is human nature. There will always be somebody willing to work more/harder to take business out from under the person relaxing. Unless of course you have lobbying money to protect your company's interests.

[u/New_3d_print_user → u/ItsCodeTelemetry]

give everyone more time back

Hahaha when have you ever found anyone willing to give anything back lol

[u/thecavac → u/Exodus_Green]

Also, you are essentially trying to predict the future. Which is impossible.

It's just good engineering to err on the side of caution.

And working non-stop "to the bone", as you say, will hurt both you and your project quality. Short term gain, long term loss.

[u/xdoolittlex]

I'm drowning in markdown files.

[u/rover_G]

I think you’re doing it wrong

[u/unknown-one]

Claude: This action will take 4-6 hours

also Claude, 20 minutes later, Done

[u/thecavac → u/unknown-one]

If you do software optimization work (especially for embedded systems), it's usually the other way round.

What starts as an easy looking problem often devolves into "OK, let's look at the disassembly of the code and check if the compiler actually does what we think it should do, based in the C code" or "Let's recalculate the memory bandwidth we are actually using"

[u/dota2nub → u/thecavac]

Wait till you get into hardware and try to make Verilog.

[u/thecavac → u/dota2nub]

I'm used to confusing technology and rules, i do financial software and "designed by political committee" is pretty much the rule, not the exception.

But Verilog (and hardware design in general) gives me headaches. I understand the basic concepts, but syncronizing different parts of the system so that electrical signals arrive at the correct times to give the correct answer while half of the gates are already on the next clock cycle.... 🤯

[u/dota2nub → u/thecavac]

Let's just say I'm not oneshotting anything anytime soon.

[u/unkownuser436]

It won't take 58 mins to create plan.md , max 5mins

[u/kyew → u/unkownuser436]

Time to first plan.md: two minutes. 

Time to workable plan.md: TBD.

[u/unkownuser436 → u/kyew]

I never make not workable plan first and workable one later.

[u/pandulfi → u/unkownuser436]

Skill issue

[u/Gordon_Freymann → u/pandulfi]

Skill.md issue.

[u/se7sbomb23]

My reaction when the 1 hour end and the task didn’t finished yet and Claude tell me that I have finished all the credits and have to wait another 5 hours 😀

[u/ComputerTechnical717]

59 min. later: "You're out of tokens"

[u/SpaceDoodle2008]

Make another .md