Live data from Hacker News

How to Design Programs (2023)

htdp.org

1–10 of 23 posts

Re: How to Design Programs (2023)

#5

How would a working Software Professional find the time to read a whole book like this?

Option 1: Have a good employer, who values learning and having highly qualified developers.

Option 2: In lack of option 1, I am afraid one will have to spend ones free time on it.

Option 3: Take a "sabattical" or whatever it is called.

Option 4: Quit job and find an option 1 employer.

Re: How to Design Programs (2023)

#6

How would a working Software Professional find the time to read a whole book like this?

If there is any profession that is built on the assumption that its practitioners constantly put aside time to stay up to date it is every profession that is even remotly connected to engineering.

Maybe many software devs don't view themselves as engineers, but engineers can be held liable if their work doesn't live up to the current technological standards.

I would say, regardless of what you do, sometimes you have to take some time for introspection, unless you plan to live with the consequences of not doing it. And reading books is part of that.

If your employer is smart they consider that. If you are smart you also consider that.

Re: How to Design Programs (2023)

#8
post #7

How would a working Software Professional find the time to read a whole book like this?

8 hours free assumming you work 1/3 and sleep the other.

*smallprint: Assuming that no eating or other recreational activity is required. Also faint echoes of "sleep a little faster" motivational speech

Re: How to Design Programs (2023)

#9
post #7

Earlier quoted context omitted.

8 hours free assumming you work 1/3 and sleep the other.

*smallprint: Assuming that no eating or other recreational activity is required. Also faint echoes of "sleep a little faster" motivational speech

Well, one can also get through a book by reading a quarter of an hour a day.

Re: How to Design Programs (2023)

#10
After more than 30 years of professional software engineering experience, I have to say that the software model described by this document is applicable and/or useful to only an extremely narrow subset of software in general. I would not recommend taking this advice too seriously.
Post reply on HN