B
baus.net
baus.net · Personal blog · on HN since 2008
Thomas Baus, a programmer, writes about network programming, such as TCP_CORK, and about software careers and the tech scene.
What HN saysHN links it for "You can't impress developers" and the TCP_CORK post, which a commenter cites when discussing socket buffering. Commenters also mention his shave kit page.
17HN people shared it
10linked it in comments
26stories submitted
594story points
2 years agolast shared
2008people per year2026
Most-shared posts
- 1You can't impress developers3 people · 427 points · first shared 2013 · 163 comments on HN
- 2On tcp cork3 people · first shared 2014
- 3You cant impress developers3 people · first shared 2013
- 4The house I was born in sold for $40002 people · 118 points · first shared 2013 · 153 comments on HN
- 5To my generation (of programmers that is)2 people · 3 points · first shared 2012 · discussion on HN
- 6I met Jack Dorsey in South Park, and all I got was this blog post1 people · 12 points · first shared 2013 · 2 comments on HN
- 7Misconstruing Salary with Professional Advancement1 people · 4 points · first shared 2015 · 1 comments on HN
- 8Beyond the technical start-up, meet Chicago's king of the question.1 people · 4 points · first shared 2013 · discussion on HN
- 9Going Serverless: Converting Yield.IO to AWS and Lambda1 people · 3 points · first shared 2018 · discussion on HN
- 10The Software Paradox1 people · 3 points · first shared 2016 · discussion on HN
- 11Your stuff has no value1 people · 2 points · first shared 2017 · discussion on HN
- 12The SwitchFlow C++ HTTP Proxy: A Postmortem1 people · 2 points · first shared 2013 · discussion on HN
- 13Note to developers: not everyone has home mail delivery1 people · 2 points · first shared 2013 · 1 comments on HN
- 14A reflection on the cost of change (or why I write software in my free time)1 people · 2 points · first shared 2013 · 1 comments on HN
- 15An apology to Zach Holman.1 people · 2 points · first shared 2013 · discussion on HN
What HN people wrote when they linked it
cmbaus · 2015-06-15
What kind of blades does the company make? Are they multi-blade?
Harry's is a great idea, but I've been happy with double edge razors for a while now: http://baus.net/shave-kit
chuckadams · 2024-05-09
Some network stacks like those in Solaris and HP/UX let you tune the "Nagle limit" in just such a fashion, up to disabling it entirely by setting it to 1. I'm not aware of it being tunable on Linux, though you can manually control the buffering using TCP_CORK. https://baus.net/on-tcp_cork/ has some nice details.
baus · 2023-01-20
I'm almost 50. Parties change. The last party I had in November was a few couples drinking wine, eating charcuterie, and listening to Jazz records. Not a bad way to spend a night in my opinion.
I still like like to be social, so I took up vinyl DJing! That kindda tempers my urge for parties: https://baus.net/miami-vinyl-dj/
gregors · 2023-01-10
I don't quite understand the corking documentation. Is this like TCP_CORK? A buffered/batch send? Can anyone point me to details?
https://docs.socketify.dev/corking.html
https://baus.net/on-tcp_cork/
stefantalpalaru · 2013-06-02
the URL was changed to http://baus.net/posts/you-cant-impress-developers/
arscan · 2013-06-02
I'm getting a "Not Found" on the link. Looks like the url changed slightly to:
http://baus.net/posts/you-cant-impress-developers/
(its not a cache, but i'll say cached here for those searching the comments for a link to the google cache)
nrivadeneira · 2013-06-02
Just tried accessing this via the HN link but it was dead. It seems this is the new location of the post:
http://baus.net/posts/you-cant-impress-developers/
LnxPrgr3 · 2012-11-03
I've seen people go to extreme lengths to avoid being a victim of overcommitted memory: http://www.baus.net/memory-management
Even after having the occasional run-in with the OOM killer and having to drive into work at 3am because sshd was among the casualties, I can't see thwarting the OS's virtual memory system like this.
Besides, if you're really that worried about uptime that falling victim to the OOM killer is an unacceptable risk, you should be preparing for surprise hardware failure too, which in my experience is much more likely to happen anyway and can be just as fatal to your "invincible" process.
cmbaus1 · 2012-04-26
I speculated that this might be the case.
http://baus.net/instagram-is-twitter-the-loser
Strangely, Chris Sacca and Jack Dorsey were both investors in Instagram and they still lost the deal. I suspect it just got to rich for them. I don't think this bodes well for Twitter.
deanmoriarty · 2018-11-01