Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Habits of Expert Software Designers

thereader.mitpress.mit.edu

Post reply on HN
Print view View original

51–60 of 148 posts

Re: Habits of Expert Software Designers

#51

Post by christiansakai »

travisjeffery wrote: post #49
christiansakai wrote: post #46

I am trying to learn more about distributed systems architecture. Currently almost finished reading "Designing Data Intensive Application". Is there any recommendation from HN what book should I read next? I am thinking - Building Microservices - Desining Distributed systems Any thoughts?

Hey, I'm currently writing a book for PragProg that's going to announced soon. It's tentaively titled "Building Distributed Services with Go", and the Go part is secondary if it's not your language of choice. It guides you through building a distributed service from beginning to end. I don't have anything to point you to at the moment other than my mailing list and I'll let you know when the book is in beta: https://…

Awesome! I will subscribe!

Re: Habits of Expert Software Designers

#52

Post by ArnoVW »

remon wrote: post #50

How on earth is content this shallow drifting to the top of HN? Is any "non expert" software designer walking away from this enlightened in some way?

This article is adapted from the book “Software Design Decoded: 66 Ways Experts Think“

I imagine the idea is that if you want to go further, you buy the book.

Re: Habits of Expert Software Designers

#57

Post by commandlinefan »

rgrau wrote: post #30

Expert Software Designers read. And do it continuously. Not only HN and medium, but big "essence" ideas that you do not get usually on day to day tasks, and mold the perception of problems and solutions. People familiar with Wirth, Kay, McCarthy, Iverson, Moore's (and pals) works have a fundamentally broader vision of problems and their solutions. It's obvious, but all those points are not learnt in a discrete manner…

> Expert Software Designers read

“Read? Books? With pages? And chapters? I don’t pay you to read, I pay you to program! And I’ve seen programming, programming is done with a keyboard, so I’d better hear typing! And I expect you to tell me exactly what you’re going to be doing, hour by hour, for the next two weeks, or ‘sprint’ or whatever you nerds call these things these days, and I’d better see lots of commits to the repository because I’m checking who’s committing the most because I don’t pay you to read and learn, I pay you to know and if you don’t already know there are a thousand foreigners lined up to do your job for ten cents a day so you’d better get in line, programmer!”

Re: Habits of Expert Software Designers

#58

Post by markus_zhang »

decasia wrote: post #15

Most of these points (like the crucial importance of context/looking around, of users, of figuring out what you're not doing, etc) are important parts of software development. But the problem is, unless you already have the requisite experience to show you what these bullet points really refer to in practice, you're not going to really make sense of this list, not in a way that will actually help you do anything diff…

I agree with you. From my perspective (I'm a BA, non-developer), for sure I agree that every abstraction should be elegant. But how to define "elegant"? I probably need years and years of GOOD experience and code reading to get that point.

Re: Habits of Expert Software Designers

#59

Post by rgrau »

commandlinefan wrote: post #57
rgrau wrote: post #30

Expert Software Designers read. And do it continuously. Not only HN and medium, but big "essence" ideas that you do not get usually on day to day tasks, and mold the perception of problems and solutions. People familiar with Wirth, Kay, McCarthy, Iverson, Moore's (and pals) works have a fundamentally broader vision of problems and their solutions. It's obvious, but all those points are not learnt in a discrete manner…

> Expert Software Designers read “Read? Books? With pages? And chapters? I don’t pay you to read, I pay you to program! And I’ve seen programming, programming is done with a keyboard, so I’d better hear typing! And I expect you to tell me exactly what you’re going to be doing, hour by hour, for the next two weeks, or ‘sprint’ or whatever you nerds call these things these days, and I’d better see lots of commits to th…

oh, hey boss!

I just bought this cherry extraloud MX-blue so you can hear me clickyclacky from your office. And created a deeplearning model to count clicks for our new pay-by-press payroll model. something something democratization :)

Post reply on HN