give the code to an LLM and have a discussion about it.

does this work? there is no more need for writing high level docs?

> does this work?

Absolutely. If you loaded this into an agentic coding harness with a decent model, I can practically guarantee it would be able to help you figure out what's going on.

> there is no more need for writing high level docs?

Absolutely not. That would be like exploring a cave without a flashlight, knowing that you could just feel your way around in the dark instead.

Code is not always self-documenting, and can often tell you how it was written, but not why.

> If you loaded this into an agentic coding harness with a decent model, I can practically guarantee it would be able to help you figure out what's going on.

My non-coder but technically savvy boss has been doing this lately to great success. It's nice because I spend less time on it since the model has taken my place for the most part.

> since the model has taken my place for the most part

Hah, you realize the same thing is going on in your boss's head right? The pie chart of Things-I-Need-stronglikedan-For just shrank tiny bit...

my last employer was using ai to rank developers on most impactful code their prs are shipping.

There are so many blogs and tutorials about this stuff in particular, I wouldn't worry about it being outside the training data distribution for modern LLMs. If you have a scarce topic in some obscure language I'd be more careful when learning from LLMs.

LLMs can tell you what the code does but not why the developer chose to do it that way.

Also, large codebases are harder to understand. But projects like these are simple to discuss with an LLM.

> LLMs can tell you what the code does but not why the developer chose to do it that way.

Do LLMs not take comments into consideration? (Serious question - I'm just getting into this stuff)

They do (it's just text), if they are there...

one of the apps I built is an app that you give it a website, it scrapes it, then places the google ads.

Over time it tries to improve the ads.

Right now it is showing a 5% click through rate over a few weeks. I have no idea if that is good or not, but it saved me the hassle of having to worry about google ads for another app

If the marketing platform works, then it would drive traffic to itself.

when agile was fairly new I worked with remote developers that had 3 locations.

My specialty is software requirements and my team was brought in to do the product management. The developers had read somewhere if you were using a database to do requirements then you were doing agile wrong.

They wanted me to write post it notes in triplicate, then fedex them to all their offices.

I use amazon kiro.

The AI first works with you to write requirements, then it produces a design, then a task list.

The helps the AI to make smaller chunks to work on, it will work on one task at a time.

I can let it run for an hour or more in this mode. Then there is lots of stuff to fix, but it is mostly correct.

Kiro also supports steering files, they are files that try to lock the AI in for common design decisions.

the price is that a lot of the context is used up with these files and kiro constantly pauses to reset the context.

mine is great, it is all posts from my groups and a few from my friends.

the answer is build it again and start selling it to other companies.

the key for managers is like business owners

1) understand what success means for their area 2) assemble a team and remove roadblocks for them to achieve 1.

1 pedal braking means evs often dont need new brake pads for 150K miles

One problem they are experiencing is rust and glazing on the pads from disuse.

They are heavier than the equivalent sized ICE so have more tire wear, but dont have to be that large in an absolute sense. Most are large luxury cars.

You’re right but one pedal drive is the wrong term. Regen braking is what you’re thinking of.

One pedal drive can still use the brake pads, regen braking is what saves brake usage regardless of one pedal drive being on or not.

Slate is coming in at around 175 inches..

If your payroll ends up being about the same, after 5 years it all evens out in the sense that you will be expensing 100% of your payroll each year (but the expensing will be 20% from each of the prior 5 years).

If your payroll is quickly growing You experience the problem on all payroll growth.

If your payroll is decreasing, you get a tax benefit. Your outgoing cash is less, but you are getting deductions from prior year expenses.

Your not taking into account the time value of money. You always want to expense sooner.

Additionally, having to wait 4 additional years to deduct that 80% is a huge drain on capital.

Combine this with higher interest rates and the effect is essentially pouring sand into the gears of the tech industry.

No, it's always strictly worse because you could have bought bonds or deployed the capital in some other way with that money.

Sure if you big enough to ride out 5 years but if your a hungry struggling bootstrapped startup, this can be game over.