HNHacker News
TopNewBestAskShowJobs

theideaofcoffee

1,181 karma · joined October 3, 2017

i don't need no stinkin' caffeine

meet.hn/city/br-Rio-de-Janeiro

I speak for both you and your employer.

technical@theideaofcoffee.com

submissionscomments
theideaofcoffee··on Software development topics I've changed my mind on after 6 years in industry
> Standups are actually useful for keeping an eye on the newbies.

If you're relying on a daily standup to keep the newbies on track, then something is deeply broken with your management and people development structure. They should be continually coached one-on-one, rather than left to fend for themselves only then to pipe up once per day. A little time investment by both the noob and someone more seasoned really, genuinely helps them to get up to speed. It's something that will pay itself back many times over in the future.

I've experienced both when I stepped in as a greenhorn, I leveled up so much faster when I had the ability to pepper questions throughout the day to someone more seasoned. And I remember feeling discouraged and listless in a culture where you don't interrupt the senior people, wait for the standup, regurgitate your problems, speak the scrum prayer every morning.

Does it cost something in terms of efficiency, or vElOCiTy? Sure, but like I said above, the returns on investment compound when you really care about developing people, and not being a slave to the scrum process.

theideaofcoffee··on A terrible way to jump into colocating your own stuff
> "oh i have it right here" and pulled two Intel NUCs out of my backpack

NUCs would be like nirvana after some of the jerry-rigged crap I've seen dragged into facilities. Maybe I'd like them to have a secondary power supply, but then again you had two, but they'd make a fantastic little router for something not too traffic heavy. Lots of utility use cases for something like that in a proper facility.

theideaofcoffee··on A terrible way to jump into colocating your own stuff
Missing step -1: find someone to get on your staff that knows what they are doing, or at least find a contractor with a good history of doing this kind of thing. After a certain point, you really shouldn't wing it. But if you're at that point, you should know if you actually need your own hardware, or if public cloud or other options are good for you. Some need their own, most don't. There's a lot of nuance there that is difficult to express in a short HN comment.
theideaofcoffee··on Our digital lives need data centers. What goes on inside them?
I'm glad someone else feels the same way, it can be kind of isolating to want to be efficient at the expense of speed. There are important features to be shitting out, dont-cha-know.

It feels the same way a neglected pothole does: the city doesn't want to send a crew out for half a day (uh oh it might cost a couple thousand bucks!) to fix a pothole that five thousand cars each and every day are running over, accumulating wear and tear, discomfort to drivers and riders, day after day, week after week. No itty-bitty investment to fix the problem that might benefit so many others, similar to how we could invest a little bit of time (city money) to fix a little inefficiency here and there (that dastardly pothole). It just makes too much sense.

theideaofcoffee··on Our digital lives need data centers. What goes on inside them?
I like to see articles about the hidden systems that make so much of the modern world work, I think it's a positive thing to allow common people to have that perspective if they're interested. However, when I do see stories about datacenters and the like, I just really sort of despair, to be perfectly honest.

I see how little the industry has changed and innovated since the 'modern' datacenter crawled out from the legacy telephone switching centers. You still see the marks (read: scars) left on the old in the new: same sized racks in width, asinine cold and hot aisles shuffling hot air around blown about by fan after fan after fan screaming away endlessly until they throw their bearings. The energy moved about among so many different interfaces, air/water/air/refrigerant/water/air and around and around and back again. It's the same feeling as railroad gauges echoing the ancient wheeled carriage ruts in the hard dirt because we can't be arsed to make anything better.

You'd think that with all of the developments of omg distributed computing that every tech dweeb loves to bandy about that they're experts in that there would be a stampede to, you know, actually make use of some new technology, moving the data and compute closer to the user (and don't talk to me about edge facilities, they're just more of the same), reduce the blast radius of the idiocy of centralization, pare down the eye watering waste of facilities like this. But no, it's still client-server everything, maybe put a copy in another region if you're feeling kinky, but the promise of decentralization and distribution hasn't really materialized. Such a large percentage of people now have phenomenal power they carry with them at all times, but they're just dumbed-down gateways to these huge black holes of resources because the control needs to remain held in the same hands as the capital that continues to build them larger and larger.

I guess what I'm trying to say is that in an ideal world that uses the technology that it develops in a sane way, these places really shouldn't exist anymore, like another comment suggested. The fundamentals are all there, it's just the incentives are so out of whack it's comical. Build bigger and bigger facilities and collect more and more data and fritter away cycle after cycle and maybe you'll increase your year-over-year by a couple dozen basis points. And since the demand is so insatiably fueled by this feedback, nothing will change. You could have minuscule neighborhood nodes scattered around a city that sips resources in comparison that does all of this in concert with the portable supercomputers we all carry, each benefiting a small handful of people at once but the beast must. be. fed.

theideaofcoffee··on Kelsey Hightower: If governments rely on FOSS, they should fund it
It’s a noble goal but as easily gamed as any other license. In this case there would be nothing stopping me from starting up a new entity and then contracting out that single service for $.01 or whatever. No revenue there, no license fee required. Just add another layer on the onion. It’s similar in difficulty as a wealth tax, just add more indirection.
theideaofcoffee··on Working in the office 5 days/week to build company culture is a myth: PwC report
Anecdote for exactly the other side: most co-workers I know who went remote are 50% more productive as before. They don’t have to waste their preciously short lives in pointless office drama, pointless meetings that could have been emails, waste their lives in cars commuting to a soulless office complex because an incompetent manager thinks that butts-in-seat time makes for a productive workforce.

I would 100% lead a full remote team, and have done so, and will never go back.

theideaofcoffee··on Comedian John Mulaney brutally roasts SF techies at Dreamforce
I am incapable of doing observational humor like John Mulaney can so I’m not even going to try. Just the quotes from the article alone are giving me life. I would have loved to have seen this in person, speaking truth to (lol) power.
theideaofcoffee··on Visual guide to SSH tunneling and port forwarding (2023)
Yep, had I known that nearly 20 years ago I would have done just that. That's the ideal way to do it now!
theideaofcoffee··on Visual guide to SSH tunneling and port forwarding (2023)
The filthiest SSH tunneling hack that I've ever done was at 3AM while in a three-way... datacenter connection. The interesting part of that, while the three facilities, spaced out over a single metro area had upstream transit connectivity to the rest of the net, only two pairs were able to reach the other due to some odd routing policies that weren't able to be resolved in time.

That meant that A could connect to B, and only B could connect to C. The data I had to move from facility A to facility C via B in the most ridiculous rsync+ssh tunnel+keys+routing shenanigan mashup I've ever done. It took a few tries to get the incantation exactly right, but it was magical seeing it all move as one.

Looking back it is super obvious how I'd do it now, but back then being green, was a huge accomplishment. I still remember the exhilaration when I confirmed everything was synced up.

theideaofcoffee··on OpenNMS: Visualize and monitor everything on your local and distributed networks
Damn, not much has changed since I last looked at the project nearly 15 years ago when evaluating it against other management packages in an academic computing center. So frustrating to have all of the words words words and not a single shot of it in action, ya know, like you’d see it when in use.
theideaofcoffee··on Lichess: Post-Mortem of Our Longest Downtime
I guess some of my questions are addressed in the latter half of the post, but I'm still puzzled why a prominent service didn't have a plan for what looked like a run of the mill hardware outage. It's hard to know exactly what happened as I'm having trouble parsing some of the post (what is a 'network connector'? is it a cable? nic?). What were some of the 'increasingly outlandish' workarounds? Are they actually standing up production hosts manually, and was that the cause of a delay or unwillingness to get new hardware goin? I think it would be important to have all of that set down either in documentation or code seeing as most of their technical staff are either volunteers, who may come and go, or part timers. Maybe they did, it's not clear.

It's also weird seeing that they are still waiting on their provider to tell them exactly what was done to the hardware to get it going again, that's usually one of the first things a tech mentions: "ok, we replaced the optics in port 1" or "I replaced that cable after seeing increased error rates", something like that.

theideaofcoffee··on Show HN: Server Uptime
Second healthchecksio. Used them recently for a quick project that “just” needed status monitoring for cron tasks. Super simple to drop a curl equivalent at the start and end and important moments in the middle. Do one thing well, yadda yadda. This one seems pretty similar in scope to hcio where you can also send simple (simple!) payloads like this project as well.
theideaofcoffee··on CrowdStrike ex-employees: 'Quality control was not part of our process'
I've commented on this before, but in this case I think it starts to fall onto the laps of the individual employees themselves by way of licensing, or at least some sort of certification system. Sure, you could skirt a test here or there, but then you'd only be shorting yourself when shit hits the fan. It'd be your license and essentially your livelihood on the line.

"Proper" engineering disciplines have similar systems like the Professional Engineer cert via the NSPE that requires designs be signed off. If you had the requirement that all software engineers (now with the certification actually bestowing them the proper title of 'engineer') sign off on their design, you could prevent the company from just finding someone else more unscrupulous to push that update or whatever through. If the entirety of the department or company is employing properly certificated people, they'd be stuck actually doing it the right way.

That's their incentive to do it correctly: sign your name to it, or lose your license, and just for drama's sake, don't collect $200, directly to jail. For the companies, employ properly licensed engineers, or risk unlimited downside liability when shit goes sideways, similar to what might happen if an engineering firm built a shoddy bridge.

Would a firm that peddles some sort of CRUD app need to go through all of this? If it handles toxic data like payments or health data or other PII, sure. Otherwise, probably not, just like you have small contracting outfits that build garden sheds or whatever being a bit different than those that maintain, say, cooling systems for nuclear plants. Perhaps a law might be written to include companies that work in certain industries or business lines to compel them to do this.

theideaofcoffee··on CrowdStrike ex-employees: 'Quality control was not part of our process'
Yes, I am very much biased toward being anti-company and I make no apologies for that. I've been in the corporate world long enough to know first-hand the sins that PR and corporate management commits on the company's behalf and the harm it does. I find information coming from the individual more reliable than having it filtered through corpo PR, legal, ass-covering nonsense, the latter group often wanting to preserve the status quo than getting out actual info.
theideaofcoffee··on CrowdStrike ex-employees: 'Quality control was not part of our process'
I just don't think a company like Crowdstrike has a leg to stand on when leveling the "disgruntled" label in the face of their, let's face it, astoundingly epic fuck up. It's the disgruntled employees that I think would have the most clear picture of what was going on, regardless of them being in QA/QC or not because they, at that point, don't really care any more and will be more forthright with their thoughts. I'd certainly trust their info more than a company yes-man which is probably where some of that opposing messaging came from.
theideaofcoffee··on CrowdStrike ex-employees: 'Quality control was not part of our process'
"We can't regulate the industry because then the US loses to China" or "regulation will kill the US competitive advantage!" responses I've had to suggesting the same and I just can't. But I agree with you 100%. If it's safety critical, it should be under even more scrutiny than other things, it shouldn't be left to self-regulating QA-like processes in profit seeking companies and has to have a bit more scrutiny before the big button gets pressed.

Edit: Disclaimer: The quotes aren't mine, just retorts I've received from others when I suggest the R-word.

theideaofcoffee··on Defend against vampires with 10 gbps network encryption
This is a great writeup! Especially for those that may want to DIY it, the how and the why and all of that, and not have to shell out for carrier-quality Layer 1 encryption devices. Nice to see that even off-the-shelf components can do it with relative ease at those rates. Also nice to see sane sysctl tunes as well. Anything to make an adversary's day a bit harder. I low key love the explanation of old 10B5 taps, something that so well and truly dead, but the legacy carries on into everything new today.

This is actually a well-trodden area of datacenter interconnect (DCI) devices that do line-rate encryption (to crazy levels like 400G+) to protect those links that may have easily accessible fibers strung along poles, for instance, to prevent just the vampirism described in the post. Packetlight, Ciena, Infinera and others.

theideaofcoffee··on Ask HN: How to store and share passwords in a company?
Lots of people suggest 1Password, and it works really well for larger or more disperse groups needing some shared vault capability, and perhaps those that want a more visual-driven web interface. Keep in mind there is the per-seat pricing for that.

What has also worked really well in the past for me and my teams, especially if they are more technical and these credentials really never need to go beyond this more technical team is setting up a single 'vault' encrypted with GPG. Each team member then gets the vault re-encrypted for them, adding them to the recipient list. While this takes a little bit of effort to get a workflow going, it keeps it out of a cloud service, if you're concerned about that, and you get to pass it around just like any other file. When someone leaves, or no longer needs access, their recipient is removed and then the file recommitted and redistributed. In the past I've had the ASCII-armored file committed in git and people just pull down a tools repo every so often.

If you are wanting to store credentials for, say, public cloud services, don't. Use roles as much as possible, don't pass around passwords, don't bother setting up individual users beyond those required to bind a role to it, grant only by roles as much as possible.

theideaofcoffee··on Twenty Years of Valgrind (2022)
Good point, there definitely is the performance hit for the observability data it gives you, but for me, that's a fair trade for the results it gets me. I can see how working with things that have more realtime-ish constraints like games would be more greatly affected. Still, works super well for systems software, so I continue to use it.
theideaofcoffee··on I'm blocking connections from AWS to my on-prem services
Yawn. Old man yells at cloud (literally). So he's taking his little netblock ball and going home because of some failed purity tests: bad or nonexistent PTRs, excessive ICMP, oh my! The gentleman's agreements that held together the early internet and web and the unwritten practices like that are long gone, get with the times, there ain't any going back to how it was. Otherwise, feel free to disconnect entirely if you don't want to deal with the new reality.

I'm going to going out on a limb and guess that all of this traffic that isn't related directly to AWS, but its customers. You can set PTRs for your allocated elastic IPs with a request to support. But then again nobody is going to do it because... it doesn't matter. It may have mattered when you were hosting with a block that you actually truly owned, before the ICANN times, but no more. No one cares. Everything is ephemeral, so why should the reverse matter when things get cycled through addresses multiple times per day? If you're seeing excessive anything, then it's probably time to reach out to the abuse contact published in the whois. Let me help you with that:

   OrgAbuseHandle: AEA8-ARIN
   OrgAbuseName:   Amazon EC2 Abuse
   OrgAbuseEmail:  trustandsafety@support.aws.com
   OrgAbuseRef:    https://rdap.arin.net/registry/entity/AEA8-ARIN

   Comment:        All abuse reports MUST include:
   Comment:        * src IP
   Comment:        * dest IP (your IP)
   Comment:        * dest port
   Comment:        * Accurate date/timestamp and timezone of activity
   Comment:        * Intensity/frequency (short log extracts)
   Comment:        * Your contact details (phone and email) Without these we will be unable to identify the correct owner of the IP address at that point in time.
Use modern features built in to modern versions of common packages and products: rate limiting, redirects, filters, and on and on. If you're just blocking to block to make some sort of statement into the void, you're just hastening that balkanization.
theideaofcoffee··on Twenty Years of Valgrind (2022)
In a complex C codebase, valgrind is absolutely indispensable for finding the last few bits of memory that may have leaked out because you got lazy and didn't free() or maybe you wrote somewhere in memory you shouldn't have, it really is like magic sometimes. I know that more recent languages (and some not so recent, looking at you, Ada!) have a lot of this built in by default, but when you need to do these things, you know you need to and it's nice to have a handy all-in-one tool to help out. It's saved me many times from myself when I was writing network code in C and I couldn't figure out where the leaks were coming from, or a performance regression by inspecting the code alone. A quick run of valgrind had that fixed in minutes.
theideaofcoffee··on The 4-chan Go programmer
I'm going to post a low-effort, non-substantive comment because I can.

That meme in the first few paragraphs made me actual lol as a recovering C programmer.

That is all.

I love seeing odd contortions of languages like this, and C has opportunity aplenty, interesting to see it in Go.

theideaofcoffee··on Frontier is about to offer 7-gig fiber across several states
I love seeing developments like this, and while Frontier wouldn't be my first choice in provider, it's a good thing that even a historically poor performer like Frontier is pushing the boundary a bit.

What I don't love seeing is the same, predictable responses every time something like this is posted. It's always the same: "oh, they'll never be able to deliver", "their subscribers will never use it, why don't they stick with 50/10", "I get by just fine on my 100Kbps ADSL", "why would anyone want to stream video". I get it, as tech people, we're predisposed to being skeptical and questioning, but why the hostility to progress? Okay then, let's just stick with dialup, because that's only anything anyone will ever need, apparently. We should be celebrating anything that pushes the art forward.

The demand will be induced, the pipes will be filled. Let's think about applications that can actually take advantage of new capabilities like this, instead of pooh-poohing every little bit of change.

theideaofcoffee··on CrowdStrike accepting the PwnieAwards for "most epic fail" at defcon
There is nothing saying that allowing for some standardization means that we have to be stuck at 2003-levels of state of the art. And actually, yes many engineering disciplines do change, Civil engineering brings in new construction techniques, methods for non-destructive testing, improvements to materials and on and on, but it doesn't do so like the coked-up industry of software does it in such a free-for-all manner. It's a proper engineering discipline because there's the control, testing the best way to do things and rolling that out.

If we (meaning software 'engineers' and I tepidly include myself in that group) had half the self control in introducing insanity like the 10000th new javascript framework to read and write to a database like the 'proper' disciplines do, maybe it would be better because there's less churn. Why does it have to move so fast? Software is diverse and inconsistent and rapidly changing because 'the industry' (coked-out developers chasing the next big hit to their resume to level up) says it should. I just don't agree that we need that amount of change to do things that amount to mutating some data. If the techniques didn't grow beyond what was cool in 2007, or they were held there until the next thing could be evaluated and trained, but the knowledge and process around them did, perhaps we'd be in a better position. I know I certainly wouldn't mind maintaining something that was created in the last decade of the previous millennium knowing it was built with some sort of self-control and discipline in mind, and that the people working on it with me had the same mindset as well.

theideaofcoffee··on Building a highly-available web service without a database
I get the desire to experiment with interesting things, but it seems like such a huge waste of time to avoid having to learn the most basic aspects of MySQL or postgres. You could "just" build on top of and be done with it, especially if you're running in a public cloud provider. I don't buy the increased RTT or troubles with concurrency issues, the latter having simple solutions by basic tuning, or breaking out your noisy customers. There's another post on their blog mentioning the possibility of adding 10 million rows per day and the challenges of indexing that. That's... literally nothing and I don't think even 10x that justifies having to engineer a custom solution.

Worse is better until you absolutely need to be less worse, then you'll know for sure. At that point you'll know your pain points and can address them more wisely than building more up front.

theideaofcoffee··on CrowdStrike's outage should not have happened
"Nah, those uppity software engineers don't need any additional training. How dare they think they have any right to tell us how to manage this roll-out" says management, "We'll just cowboy this update and wipe out 8.5 million systems. Besides, it's not like they're working on nuclear reactors, yeah? How complex could it be?"

You're just proving my point in that it's a CTO that dismisses the argument in a rather childish way. They would be the one to be told 'no' by the now-professional software engineers when their license and livelihood is on the line while being pressured to do something that goes against their recommendation. Funny how that power dynamic changes when there's something real on the line and not just an inflated title, huh?

Perhaps if those aerospace and software engineers that attempted to blow the whistle at Boeing were successful and were empowered via their license to say enough and stop development on MCAS, there wouldn’t be 300+ dead people because of a software change rammed through by management. The licensure ain’t just window dressing. It has real, actual impact on real human lives. Don’t be so dismissive.

theideaofcoffee··on CrowdStrike's outage should not have happened
Same, which is why I bristle at my title containing "engineer" as I don't have a PE. If most software engineers want to legitimately call themselves engineers, the field should be formalized as an engineering discipline, including coursework, certification/licensure and, better yet, apprenticeship-like experiences required for "real" engineers working toward their Professional Engineer license.

Edit: I'd add this goes double when working on safety-critical code, or anything touching protected health data, or payment/financial data. It's just too toxic and valuable to leave to a chance change.

theideaofcoffee··on Prevention of HIV
Thank you for adding this here, I was working on compiling something similar for another comment on the thread. This is pretty much the gold standard and yeah those that keep up on preventatives and testing are usually the least likely to pass anything along. More information is better, not less! These puritanical views on human sexuality, like the comment above yours to which you're responding and others, only cause more hurt and don't really have any sort of deterrent effect. Peeps be fuckin', nothing you can do to stop it besides get the best info and treatments out there.
theideaofcoffee··on Prevention of HIV
Are you a virologist, epidemiologist or other specialist with peer-reviewed research pointing in the direction opposite to the conclusions in the paper above? If so, you should publish your findings because that would be a huge refutation of current knowledge and would possibly help the epidemiology of transmission in the greater public.

Until then, I'll take the word of public health practitioners who've been steeped in the field for their entire careers. Their work has been significant enough to be published in Lancet which is a pretty good signal to this layman (though with a bachelor's of science in an unrelated scientific field, so no stranger to reading primary literature).

← PreviousPage 8 of 14Next →