Live data from Hacker News

Minimal Viable Programs (2014)

joearms.github.io

11–12 of 12 posts

Re: Minimal Viable Programs (2014)

#11
post #3

Amusing advice from this article: > If you want a job done find the busiest person you know and give them an extra job. This is because the reason they are busy is that lots of people want them to do things because they are good at doing things and that’s why they are busy.

It's so amusing that is almost sad - I know such people around me, they get constantly abused by their peers, don't have the necessary means to deliver great results and get systematically bashed for that. So their situation is not so much for their skills as for their weakness (of character).

Re: Minimal Viable Programs (2014)

#12
post #9

> A minimal viable program is the smallest program that solves a particular problem. It is small and beautiful. It has no additional features. A problem is rarely well-defined. Alternately, you can encapsulate small and beautiful programs into classes, and connect objects at runtime to solve more complex problems. OO reinvented. In his case, he prefers to use the shell to do the plumbing instead of another language.

"you can encapsulate small and beautiful programs into classes, and connect objects at runtime to solve more complex problems"

Then in order to ease the integration between those classes you start reshaping them a little bit (adding things that "would not be essential") and thus they are gaining in this regard something very similar to the same features that we were talking about.

Post reply on HN