My comparison to waterfall was a reductionistic take on the specifications up-front before coding starts aspect. If comparing it to the full waterfall process then it is definitely a fresh take!
It sounds a bit like the Waterfall model. It became highly unfashionable in the 90s, maybe even earlier.
I miss the passive nature of the web. A page got loaded and then it was idle. Now I can stare at a page of text with my cpu spinning at 100% in the background, it adds nothing extra to my experience except for a quiet…
The TDD advocates I have been exposed to are mostly cargo culting consultants and this alone makes me very sceptical. It has some good core ideas but I find that in practice it leads to unit tests that are highly…
This "article" is just an ad.
I would definetly pick the store with the hacker newsish website!
I don't like people saying just hello and expecting me to answer before they get to the point. If I see the message and immediately respond hello back then I have to sit and wait and watch the 'person is writing'…
..in my experience it can also lead to antagonistic thoughts about people who I have never met and only know through the code they wrote :)
Yes definitely. But only reading the code and looking at the history can sometimes be enough to build the picture when the same names repeatedly show up in troublesome code
If you are working on an old code base for a reasonable time I recommend to get to know the old developers. Check out the commit history, who wrote what, talk with them a bit if they are still around to get a feel for…
That critique is a bit unspecific but I tend to agree. I have heard good a stuff about "gradulizer" though. It uses a gradual type system instead of dialyzers success typing. https://github.com/josefs/Gradualizer
A variant of no 3 is used for some large scale telecom equipment supporting multi millions of attached users with serious uptime requirements. State is distributed and handled locally and replicated to a sibling node…
Agree with this. I obviously comment on bugs and also convoluted code that I know will be hard to understand later. If it is just small details it is easier to just change them myself when I inevitably have to revisit…
Seems like a common theme with the explosion of new programming related projects. Everyone wants to be innovative, why check first when it's more fun to reinvent the wheel (now done in Rust :P)
One Chinese I talked to said there are two reasons that can play into this pressure. First reason is that the grandparents probably had the same situation themselves, they were raised by their grandparents, so now they…
I notice that it's not uncommon for American recipes to be tied to a specific brand of sauce or similar. I don't see this as often in "European" recepies, here usually the recipe is broken down further or listing a…
I love the C2 wiki! Such a nice collection of discussions and ideas. When I encounter some predicament or some ideas pop into my mind about a particular subject I always check C2 to see what they have on it. Reading…
My comparison to waterfall was a reductionistic take on the specifications up-front before coding starts aspect. If comparing it to the full waterfall process then it is definitely a fresh take!
It sounds a bit like the Waterfall model. It became highly unfashionable in the 90s, maybe even earlier.
I miss the passive nature of the web. A page got loaded and then it was idle. Now I can stare at a page of text with my cpu spinning at 100% in the background, it adds nothing extra to my experience except for a quiet…
The TDD advocates I have been exposed to are mostly cargo culting consultants and this alone makes me very sceptical. It has some good core ideas but I find that in practice it leads to unit tests that are highly…
This "article" is just an ad.
I would definetly pick the store with the hacker newsish website!
I don't like people saying just hello and expecting me to answer before they get to the point. If I see the message and immediately respond hello back then I have to sit and wait and watch the 'person is writing'…
..in my experience it can also lead to antagonistic thoughts about people who I have never met and only know through the code they wrote :)
Yes definitely. But only reading the code and looking at the history can sometimes be enough to build the picture when the same names repeatedly show up in troublesome code
If you are working on an old code base for a reasonable time I recommend to get to know the old developers. Check out the commit history, who wrote what, talk with them a bit if they are still around to get a feel for…
That critique is a bit unspecific but I tend to agree. I have heard good a stuff about "gradulizer" though. It uses a gradual type system instead of dialyzers success typing. https://github.com/josefs/Gradualizer
A variant of no 3 is used for some large scale telecom equipment supporting multi millions of attached users with serious uptime requirements. State is distributed and handled locally and replicated to a sibling node…
Agree with this. I obviously comment on bugs and also convoluted code that I know will be hard to understand later. If it is just small details it is easier to just change them myself when I inevitably have to revisit…
Seems like a common theme with the explosion of new programming related projects. Everyone wants to be innovative, why check first when it's more fun to reinvent the wheel (now done in Rust :P)
One Chinese I talked to said there are two reasons that can play into this pressure. First reason is that the grandparents probably had the same situation themselves, they were raised by their grandparents, so now they…
I notice that it's not uncommon for American recipes to be tied to a specific brand of sauce or similar. I don't see this as often in "European" recepies, here usually the recipe is broken down further or listing a…
I love the C2 wiki! Such a nice collection of discussions and ideas. When I encounter some predicament or some ideas pop into my mind about a particular subject I always check C2 to see what they have on it. Reading…