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 How the electricity markets respond to a nuclear trip
Instead of that energy being directed to the turbines to convert the thermal energy into rotational energy (and thus it to electricity), the reactor begins cooling from the primary reactions (but not completely since secondary reactions/decay still are going) since there is no reaction heat (reactor idled). All of that excess residual heat contained in the mass of the fuel and reactor water is carried away by the cooling water loop, and either out to the cooling tower where it evaporates and releases its energy, or through the next stages of the loop into the cooling supply, most likely a neighboring river or lake.
theideaofcoffee··on Ask HN: Weirdest Computer Architecture?
I was hoping someone was going to mention Dave Ackley and the MFM. It has really burrowed down into my mind and I start to see applications of it even when I'm not looking out for it. It really is a mindfuck and I wish it was something that was a bit more top of mind for people. I really think it will be useful when computation becomes even more ubiquitous than it is now, how we'll have to think even more about failure, and make it a first class citizen.

Though I think it will be difficult to switch the narrative of better-performance-at-all-costs mindset toward something like this. For almost every application, you'd probably be better off worrying about integrity than raw speed.

theideaofcoffee··on Was the Internet created to survive a nuclear strike? (2022)
Google Fiber was infamous for doing it this way, called "microtrenching" or "nanotrenching", where they either cut a trench into pavement and lay the cable into that and fill over with asphalt or other material. When done poorly (read: most of the installs that they've done), it erodes the road surface and the base and causes all sorts of problems [0] [1] [2] [3]

Also lots of providers just string up cable on poles, which are routinely snagged by trucks, shot by ammunition, run into by cars, etc etc, so even more vulnerable than shallow burial. Some of these cables are major links so damage can cause wide-reaching problems. No match for an out of control sedan, let along a nuclear strike. [4] [5]

[0] https://www.techrepublic.com/article/google-fiber-is-using-a...

[1] https://wpln.org/post/google-fiber-disruptions-have-some-say...

[2] https://www.nashvillescene.com/news/pithinthewind/google-tre...

[3] https://arstechnica.com/information-technology/2019/02/googl...

[4] https://www.wmur.com/article/crash-manchester-comcast-servic...

[5] https://www.cbsnews.com/sacramento/news/crash-vandalism-comc...

and etc

theideaofcoffee··on Smart jerks aren't worth it
This has been my experience as well, it boils down to them mostly being unheard, which causes frustration which can manifest itself as us-vs-them. Taking the time and hearing them out, and like you did, just working with them and hearing them helps a ton. I can count the number of actual jerks I’ve crossed paths with in my career on less than four fingers over nearly 20 years. The other “jerks” just need a little peace, love and understanding.
theideaofcoffee··on CrowdStrike fixes start at "reboot up to 15 times", gets more complex from there
None whatsoever, I don’t have any affiliation. But this is usually how it happens, knowing what I’ve seen first-hand in my day-to-day and just keeping up on the insanity of the industry.
theideaofcoffee··on CrowdStrike fixes start at "reboot up to 15 times", gets more complex from there
> “Every now and then a trigger has to be pulled.” > “Or not pulled. It’s hard to know which in your pajamas, Q.”

It’ll probably turn out that this update was pushed out against the strident, loud warnings of some small dev group within the company, and overruled by the all-knowing managerial class to keep up an OKR. They’ll have been warned six ways to Sunday but...

I’d definitely be not be the one pushing the big red button.

theideaofcoffee··on Panic at the Job Market
> Then, of course, you get rejected under some false pretense of “not having enough experience” when you’re trying to promote developing fixes to their seemingly decaying platform ^4

>> 4 There’s a continual disconnect where people with experience can see problems then construct easy and rapid to implement solutions, but people with less experience think every little bug fix is a “we don’t have time to stop the world for 6 months so we can never fix anything!” problem. We get excited to fix problems because we see fixing problems is tractable and we can implement these fixes in days instead of months as opposed to others don’t understand how everything works. It’s amazing how the simple practice of just doing the work solves many problems sooner than many people think is possible.

I didn't expect a mind reading today. It's kind of cathartic to read about someone experiencing similar problems and know that it's just a people thing after all, the tech really doesn't exist, just the individuals doing it.

theideaofcoffee··on PySkyWiFi: Free stupid wi-fi on long-haul flights
This is bonkers and I love it. A great hack in spirit but also a good primer on how a fundamental protocol like TCP kinda-if-you-squint-sorta powers everything else.

I wish I thought of it on my last trans-atlantic!

theideaofcoffee··on Python Has Too Many Package Managers
Thank you for that context!
theideaofcoffee··on Python Has Too Many Package Managers
Maybe it's just a joke, but for those that don't know that is Perl's motto and even better because there's the venerable, wonderful CPAN [0] which is the de facto package repository for the language.

[0] https://www.cpan.org/

theideaofcoffee··on The saddest "Just Ship It" story ever (2020)
I feel this deep in my bones. I worked on <some project> a long while back because I wanted to scratch an itch, and I thought that some of the problems I was seeing, hey, maybe someone else was having them too. So I start kinda-sorta-half-heartedly exploring the idea, writing some pilot code, then I discovered hacker news. And oh boy did people have things to say about the general problem, it's impossible to solve, no one should waste their time, we can just <do the drop box thing and wire up ninety five things and make it shamble along>, definitely no need to waste time trying to implement something new from scratch.

Then I dropped it, because, hey, the glitterati of hacker news and all of the others must be right, huh? I let it wither, while working on other things, working for other people, making them wealthier, while all in the back of my mind I keep thinking: "maybe I should keep working on it."

Services doing the same exact thing started popping up. They get traction. Users are mostly happy with what they were doing, but they didn't have half of the features that I had already implemented in the code that hadn't seen any use outside of my testing environment. Some take off so well they have a now-publicly traded company doing the same thing. Ten years after I started my little project.

Fuck.

Lesson learned. The naivete of youth is a harsh teacher. Work on it. Put more effort into it. Ship it. Go with your gut--you probably have a better sense than you think you do of what will work and what won't. Ignore the hivemind. Don't leave room for the regret you will inevitably feel when you're scooped.

theideaofcoffee··on Ask HN: Who is hiring? (July 2024)
This has been my experience too having been a long time in the SRE niche, and I think it's a factor of a couple of things: the market being over-saturated both from the huge numbers of layoffs happening in the recent past and the hangers-on/bootcamp attendees expecting outsized comp with little experience so postings get absolutely flooded with applicants. I spoke with a hiring manager just within the last few weeks and they said for a senior-ish position, they received almost 1000 CVs. Were they all qualified? Who knows, it seems like it would be almost impossible to find the true gems in a pile of shit like that.

A lot of these companies also seem to be reaching beyond their grasp as well. I don't think a lot of them necessarily have the vision, nor the wisdom on their staff to recognize a well-rounded background, especially if there isn't the blaring siren of a FAANG on someone's resume. They're simply not equipped to dig in. It's probably also a matter of raw number of years, they're afraid that if you join, you'll get bored then they'll be back to square one (been there).

theideaofcoffee··on A bunch of programming advice I'd give to myself 15 years ago
> If you (or your team) are shooting yourselves in the foot constantly, fix the gun

This is a reasonable step to take if you're working in a reasonable company with reasonable "management". If you're unlucky enough to be working under a manager that refuses to recognize there is a problem, even with compelling data, prepare for pain. In that case nothing is allowed to be done because "well, that's how we've always done it and doing something about it might upset someone". It's really time to quit and find something new at that point because there is generally no hope of turning that around.

> If you can’t easily explain why something is difficult, then it’s incidental complexity, which is probably worth addressing

See above. "That's how we've always done it, and someone is used to that work flow, so we can't change it." Sometimes this will lead to a legitimate Chesterton's Fence situation, in which case you'd want to regroup and rethink it. Otherwise, the batshit insane is the default. Target the latter.

> Try to solve bugs one layer deeper

"There is no time to do that! We have so many other projects!" While being blind to the fact (or better yet, burying their head in the sand and trying to ignore) that it's all self-induced.

> Don’t underestimate the value of digging into history to investigate some bugs

"We can't change that because one of our people close to management made that decision and it might drive them away." Good, get them out, that's the only way to really fix it. Ideally if the management that hired them is pushed out too.

> When working on a team, you should usually ask the question

"Who are you to question our wisdom? Who are you to suggest something else, it's working in production."

These are great things to start conversations, but you have to start them in an organization that is willing to change and be willing to take your advice to heart. Don't waste your precious life trying to change what can't be change, no matter how much you want to see it change.

theideaofcoffee··on Ask HN: What's Wrong with IRC?
This has all the energy of the infamous response to Dropbox back in the day [0]. "Just set up a client, and a bouncer, and adjust your retention policy in this text file buried three levels deep and make sure you have enough disk space, and...", when at the end Julie in HR just wants to keep an eye on what happened in the #watercooler channel when she's away on vacay.

[0] https://news.ycombinator.com/item?id=9224

theideaofcoffee··on Ask HN: What's Wrong with IRC?
Being able to search in the past for a half-remembered conversation sounds great until you have idiotic, asinine corporate data retention policies that require anything beyond 90 days to be deleted anyway, for some bullshit reason like being open to litigation or whatever and that being subject to discovery.

Then that's implemented with no warning to be able to migrate important info out into a wiki or other documentation. So in the end, no better than IRC really, but I get it, not a Slack problem, but allowing that whiplash at a click of a button doesn't help. Slack seems to help paper over deep cultural problems in a way that makes it all colorful and squishy.

But as other seem to agree, it's pretty bad at keeping anything organized like you want to be as an info repo, there are tools that are geared toward that specifically. Don't crowbar one into the other.

theideaofcoffee··on The economics of the Birkin handbag
Same, I drove a factory-fresh F140 v12 GTC4Lusso straight off the line in Maranello while they were still being produced, and having background in German-built cars, it’s light years of difference. If I could have bought that same day I 100% would have. They’re that good.
theideaofcoffee··on The unbearable sorrow of Apple Weather
It looks like the poster realized a global setting messed everything up but there’s still... everything else about that wretched app. Even on the best, cleanest, fastest, newest, pick your adjective, connection, it’s still so... bad. Nothing loads quickly, I stand there for what seems like ages to get temperatures for my city, every time. I hate opening it and trying to get info from it. The map for clouds or precip is even worse, failing to load the one part of the map that I want to see.

It’s by far Apple’s worst built-in app on the iphone, by far. I wish they’d give it some love, moreso after having bought out Dark Sky.

theideaofcoffee··on Innovation heroes are a sign of a dysfunctional organization
I know that feeling all too well. And it's such a hard truth that devoting just a little time, letting some projects slip just a bit, to fixing those systemic problems could make lots of others go away, it's just next to impossible to get people to want to change. I've found because people don't want to, they want to keep doing what they're doing and are scared of anything new because that may mean either they'd have to retrain, or more pathologically, that their position is threatened.

It all comes down to the people. The right people can make all the difference in something like that, the wrong people make it miserable for the rest.

theideaofcoffee··on Innovation heroes are a sign of a dysfunctional organization
The idea of calcified culture and process isn't limited to large bureaucracies and government institutions. It's just as prevalent in orgs barely tipping over three figures' worth of people. In many ways, seeing it from both the large and the small, the smaller ones are often the most difficult to change because there are one or two people touching everything. Most often they have been there for a long time and such having the 'trust' of management so the bare minimum of 'new' ideas, and new being the state-of-the-art of the industry ten years ago, because they might have to adapt.

Playing the innovation hero in that kind of org is dangerous, and I have the battle scars, the burn-out and resentment to prove it. Others have pointed out that the point of the power structures is to self-perpetuate and any threat to that is swiftly dealt with.

It's just so sad to see, all because people fear change. I don't know how to change that other than replacing those lifers and swapping out management.

Now I know what to look for and am willing to bounce at the first sign of it.

theideaofcoffee··on 1/25-scale Cray C90 wristwatch
Will a future design include the external heat exchanger unit? Maybe belt attached? The SSD on the other wrist, perhaps? :)

I love to see these projects keeping the legacy of these old, great machines alive, if not running some fraction of unicos, at least aesthetically.

theideaofcoffee··on Why Triplebyte Failed
Maybe it’s time to start thinking about doing to software what has been done with other professional fields: licensing and checking out of various levels. If I have to spend 30 hours or so learning, practicing and demonstrating my knowledge about aircraft instrument procedures before I can attempt that as a pilot in real airspace, maybe it’s not that big of a jump that we’d license different software features, and going outside of those bounds would be subject to loss of license.

Then we’d know this set of language features you’re familiar enough with to hold that cert. It might cut down on the waste and proliferation of useless tech that seems to be strangling the industry because people just want it on their resume.

It would do enough to dissuade companies from hiring non-licensed engineers (hey you could actually call yourself and engineer and not feel like an imposter), and would put a hard liability on things that definitely need it: financial and health data, which seems to be ripe for exploit and disclosure.

One way or another the insanity of the current system needs to stop.

theideaofcoffee··on South Pole Water Infrastructure
It's always fun seeing these posts, it's a look into such a strange way of living and supporting life. And there's something subtly terrifying about the whole operation too, seemingly teetering on a knife's edge between the ever-forward marching of entropy and all of the energy they need to put in to keep that in check, even more so with it being so cold. How fast it could collapse if, say, there was a generator problem and how diesel fuel is the only thing that's keeping it afloat.

I'd love to see a post, maybe there is, about maintenance of all of this, perhaps a story or two about an issue that maybe had some existential threat to the station and how it was overcome. I look at the majority of the infrastructure there and just keep in the back of my mind how fragile it all seems. And yes, obviously there are redundancies, but even with redundancy, things can still fail, they exist in the physical world after all.

theideaofcoffee··on Whiteboard interviews are a test of obedience, not intelligence
Au contraire, I think those that recognize the farce for what it is are better suited to evaluating objectively, rather than cargo culting the process cribbed from more bullshit artists from faang and others.
theideaofcoffee··on Whiteboard interviews are a test of obedience, not intelligence
Same, I've joined a number of orgs that seem to fit well with what I was looking for, but even the answers to my (rather pointed) questions during the interview and offer negotiation turned out to be outright lies that caused both of us to suffer a ton of wasted time and effort. TBYB would save a bunch of time, but so would people dropping the bullshit acts.
theideaofcoffee··on Whiteboard interviews are a test of obedience, not intelligence
> never thought about obedience in any aspect.

What demonstrates obedience more than having to solve a problem against the expectations of someone holding something of value over your head? "If you don't do as we say in the way we tell you to say it, you don't get this <thing>." No matter you may have a different perspective on solving the problem, even going so far as to dismiss it outright, it's all about the rubric. No subtlety, no interpretation allowed. Make it easier for your interviewer masters.

theideaofcoffee··on Whiteboard interviews are a test of obedience, not intelligence
It's the asymmetry of time invested that gets me. You (the interviewee) are expected to put in your personal time preparing a hastily thought out and assigned example problem that usually has, in my experience, nothing to do with the position, on top of investing even more time talking to interviewers beyond that. The interviewers are already getting paid to do that on their side so you're suffering opportunity cost not being able to take other interviews that may be more relevant. It's just a completely whack system and all about the power imbalance. But then again, whack is describing this stupid industry more and more these days so I guess it fits.

Personally, I think the main post hits it right on.

theideaofcoffee··on Fusion tech finds geothermal energy application
More than we could ever hope to extract at even heightened future consumption levels, which you could take to mean pretty much impossible, see a past comment of mine along these lines: [0]

[0] https://news.ycombinator.com/item?id=38850786

theideaofcoffee··on How to copy a file from a 30-year-old laptop
He says that there are internal speakers, but no jack. If it were me, I would have cracked the case open and tapped into the audio going to the speakers directly and recorded it from another device, but then again this makes a much more satisfying hack.
theideaofcoffee··on Coding interviews are stupid (ish)
Even a skills-based test like welding, you do run up against a limited number of real standards, unlike coding interviews. What materials are you joining, measurements, what process are you using, do we have particular requirements about penetration, non-destructive test results, tensile strength, etc etc. That's the problem with modern development not having a central certification or licensure or a standards board/bar, everyone tests something different even if they think they're testing the same thing and it's a depressing mess.
theideaofcoffee··on Coding interviews are stupid (ish)
I'm not op, but I have had to do this a few times because of the same reasons. You pause, take a breath and kindly say "thank you for the opportunity, but at this time I don't think this is the right fit" and leave it at that. No need to embellish, or add extraneous detail or think you're being awkward because they will do the same thing if they don't want to go further in the process with you. It's just business, treat it as such.
← PreviousPage 9 of 14Next →