News for hackers. Stuff that matters.
Re:Avoid blundering: 80% of a winning strategy by none_to_remain on Wednesday April 03, 2024 @01:08AM (#39913785)
Creating code is the lowest level of programming.

Deleting code is much more refined.

Preventing code is sublime.

Re:Avoid blundering: 80% of a winning strategy by Jensson on Wednesday April 03, 2024 @01:38AM (#39913964)
This leads to analysis paralysis. Building things helps you think clearer.
Re:Avoid blundering: 80% of a winning strategy by Buttons840 on Wednesday April 03, 2024 @04:20AM (#39914816)
You don't have to save everything you build. Many times I've implemented a feature and felt unsatisfied with it, reverted, and built the same thing again.
Re:Avoid blundering: 80% of a winning strategy by otterley on Wednesday April 03, 2024 @03:04AM (#39914418)
I’ve learned at Amazon that writing about what you want to build, and why, and why not do something else - in a way that others can clearly comprehend, and before ever touching a line of code - helps you think even more clearly.
Re:Avoid blundering: 80% of a winning strategy by ffsm8 on Wednesday April 03, 2024 @04:46AM (#39914930)
It really doesn't, unless you've already implemented a variation of the thing before.

There is a time for reflection and planning/thinking about a given software problem, but you're mostly wasting time doing so in-depth before you've done/looked through a rudimentary implementation.

Your planned architecture will be worse then the one from the person that interated several times while introspecting the resulting code, discovering misconceptions on the way.

Do note that this initial implementation is only there to learn the domain of the software, basically.

The phase can be skipped if you're not really changing anything and mostly just reimplement something you've done before. At that point, you're not doing something new however.

Re:Avoid blundering: 80% of a winning strategy by lioeters on Wednesday April 03, 2024 @06:05AM (#39915452)
> initial implementation is only there to learn the domain

I've been trying to do a kind of documentation-driven development, where I write a fairly detailed README file before I write a single line of code. It hasn't gone as smoothly as I imagined, I think it takes practice to get more effective - similar to test-driven dev. And it made me realize my usual approach is "to think by coding", and to explore the problem space with a rough draft of a program.

It must be a common approach, as I've heard people say "Throw away the first draft." Not only in programming but about writing in general. Ah, there's even a term for it:

Throwaway prototyping - https://en.wikipedia.org/wiki/Software_prototyping#Throwaway...

Re:Avoid blundering: 80% of a winning strategy by exceptione on Wednesday April 03, 2024 @04:50AM (#39914950)
I am interested, is there some public material about this method?
Re:Avoid blundering: 80% of a winning strategy by marklar423 on Wednesday April 03, 2024 @08:39AM (#39916673)
It's basically just writing a design document; Google has a similar culture.

I suppose if you're not actually showing it to anybody it becomes rubber ducking via design document.

Re:Avoid blundering: 80% of a winning strategy by office_drone on Wednesday April 03, 2024 @11:02AM (#39918406)
Re:Avoid blundering: 80% of a winning strategy by CuriouslyC on Wednesday April 03, 2024 @08:34AM (#39916620)
While I disagree with this approach in general - manually executing a task and following the data flow is the best way to understand a new system - I will say that with the rise of LLMs, writing documentation, stubs and comments first may be the fastest way to bootstrap a new project.
Re:Avoid blundering: 80% of a winning strategy by taneq on Wednesday April 03, 2024 @08:48AM (#39916752)
Maybe it does for some people but based on all of the functional specifications I've implemented over the years, they are by far the exception. Maybe designing and documenting first is OK if it's done by people who've already learned how systems work by building and maintaining a lot of them, though.
Re:Avoid blundering: 80% of a winning strategy by nradov on Wednesday April 03, 2024 @09:35AM (#39917267)
The documents used in Amazon at that lifecycle stage aren't functional specifications. The point is to justify launching a few project to management. You should be able to clearly explain why it's worth expending resources.
Re:Avoid blundering: 80% of a winning strategy by high_5 on Wednesday April 03, 2024 @05:13AM (#39915067)
Not necessarily. You might end up just building things on top of things spiral which reduces the ability to think clearly.
Re:Avoid blundering: 80% of a winning strategy by ambicapter on Wednesday April 03, 2024 @08:50AM (#39916771)
You can build a ton of things and not put them in production (to then pay the price of what you built). Practice makes perfect then.
Re:Avoid blundering: 80% of a winning strategy by adql on Wednesday April 03, 2024 @10:35AM (#39918072)
Designing does. Building and using it is for confirming or revoking any prior assumptions you had about the initial design to improve it.

Most of the thinking should be put into designing and then revising the design, the "building" should be the simplest part.

Re:Avoid blundering: 80% of a winning strategy by bee_rider on Wednesday April 03, 2024 @01:44AM (#39914002)
Is this true?

I find creating, then deleting to be more grounding. Explore a couple paths and pick the good one, don’t just stay home.

Re:Avoid blundering: 80% of a winning strategy by lazyasciiart on Wednesday April 03, 2024 @03:05AM (#39914424)
Some ideas don’t have a good path - they are just going to suck time and energy until cancelled. Like, the last one I’m thinking of: way out of our core product, there are others out there that are pretty good already, it got proposed as a “quick win” which was absolutely delusional, and the winning argument for why we went ahead and built it was that version 2 would do all the extra work that did tie it back to our product and made it worth doing.

Sadly, I failed at preventing it, so the team spent more than twice as long as (they) predicted to build something half as functional and surprise, no v2 will happen.

Re:Avoid blundering: 80% of a winning strategy by appplication on Wednesday April 03, 2024 @01:42AM (#39913993)
Love this, I’m going to steal it