Hacker Newsnew | past | comments | ask | show | jobs | submit | pschoeps's commentslogin

I really love the Steampipe and its approach to synthesis, its a lot of fun:

https://www.reddit.com/r/synthesizers/comments/1j7hgoo/makin...

Erica synths makes really solid hardware too.


The first thing I did when I loaded this page was add 3 css rules (margin, line height, font size). Like I get purity, but c'mon.


This seems more like a very skilled caregiver to me, I would be absolutely overwhelmed in this position.


Which is quite remarkable, because up until less than a century ago when women “entered the workforce” virtually every woman who had ever lived somehow managed to care for her 3+ children.

Incidentally, large families do scale sublinearly with respect to the parents. The reason why is that even with merely natural spacing by the time they have a fourth child, the oldest is in a position to provide significant assistance. Every mother with a large family that I’ve spoken to confirms that the difficulty peaks with the third child and then plateaus.


It is remarkable. I have one child, and it is by far the hardest thing I've ever done - far harder than any job I've had. It doesn't help that both parents are working full time. Maybe parenting has changed recently and we are too hands-on, but I can't imagine having 2, much less 3+ running around. Even if one of us stops working to raise the kids full time, it's way more taxing, physically and mentally, than working a white collar job and paying for child care.



I recall before we lived in nuclear families [somewhat recent phenomenon] communal raising was commonplace. Grandparents, aunts, uncles, neigbours, etc. would come help.


Dude! I was just thinking of forking your gem to implement these changes myself. You are so fast, thanks.


About 5 years ago when I was just starting out I found myself designing a responsive course builder. My solution to a responsive interface at this time involved sending a very large stringified HTML file over websockets.

This wasn't a huge problem, but the configuration on Action Cable (Rails wrapper around websockets), logged the entire contents of the message to STDOUT. At a moderate scale, this combined with a memory leak bug in Docker that crashed our application every time one of our staff members tried to perform a routine action on our web app. This action resulted in a single log line of > 64kb, which Docker was unable to handle.

All of this would have been more manageable if it hadn't first surfaced while I was taxiing on a flight from Detroit to San Francisco (I was the only full time engineer). I managed to restart the application via our hosting providers mobile web interface, and frantically instructed everyone to NOT TOUCH ANYTHING until I landed.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: