HNHacker News
TopNewBestAskShowJobs

ufmace

7,508 karma · joined February 28, 2013

submissionscomments
ufmace··on Panic at the Job Market
Yup, I've developed a workflow that starts with writing a brain-dead easy fizzbuzz and gradually adds features and complexity. The way I've done it, it gives you a way to judge levels as well as basic competency.

If you can't, or can just barely, complete fizzbuzz in the allowed interview time with a lot of coaching in your language of choice, then you definitely aren't ready to work as a SWE. If you breeze through all my extra sections in half the time, then you're great. Partway through, and you're probably a decent junior to senior engineer.

ufmace··on AT&T says criminals stole phone records of 'nearly all' customers in data breach
It's pretty much the definition of a functional state that the police can gather more resources faster than any group of criminals. By the time you gather enough criminals to hold off the police for even a few minutes, most of the time, combined with the sibling's point of not that much physical money being stored at banks, there's not much money to go around to that many people.
ufmace··on Ask HN: Freelancer's Dilemma – Client Won't Pay Despite Clear Agreement
It's a good video, but I think some people may miss the point.

You SHOULD be working with a good lawyer ahead of time. You should NOT be regularly suing your clients. Actually suing is expensive, time-consuming, and painful.

You should have a solid, enforceable contract set up ahead of time that you require new clients to sign, and get your lawyer involved if they want to change anything. The contract should ensure that you are within your rights to stop work and take away things they want if they aren't paying on time. If you do it right, you have a smooth and easy escalation path for non-payment, they're the ones who find themselves in a bad situation and have the option of either trying to sue you or just pay you the originally-agreed-upon amount.

I'm not a lawyer or your lawyer and don't even know what jurisdiction anyone is in, so don't do anything without consulting one. But the idea is something like, you only transfer control of servers and services to the customer upon being paid in full, no exceptions, and if they are behind on payment by some particular time and amount, you are explicitly within your rights to shut down services or block their access until such time as their account is paid up.

It's interesting how a good contract is kind of like a good program. The happy case is only like 20% of the work, the other 80% of the code or contract is all about detailing every possible way the happy case could go wrong and exactly what happens when each particular way of going wrong happens.

ufmace··on Peer review is essential for science. Unfortunately, it's broken
In a perfect world, studies should not only be required to include the code, any of the following should also be a reason to reject a publication:

* The code can't be run outside the original researcher's undocumented special snowflake system

* A fellow scientist who understands the domain can't understand what the code is doing and so is unable to verify that it isn't making any mistakes

* It'd be really nice if there were some sort of test cases that could verify that the code in question produced results in line with what the scope of the paper in question considers to be established science in that domain before it was applied to the experimental data - probably not always possible, but it'd be good to at least try

Yeah I know this doesn't touch the dozens of other reasons the whole institution is in trouble, and for those reasons usually nobody who has the skill and time to properly review the code actually reviews it carefully. For that matter, most scientists aren't very good at writing code that's easy to understand and will run everywhere. Just one more set of things that ought to go on the list of things that really should be changed.

ufmace··on How to get root access to your Sleep Number bed
Well yeah. But:

1. That's exactly why I prefer a plain old analog mattress that needs zero tech or support from anyone ever

2. Even with that being the case, for the average consumer who wants an electronic/controllable bed, it's still a better deal than anything that requires a custom home automation setup. Check out the prices for hiring somebody who can actually troubleshoot that.

ufmace··on How to get root access to your Sleep Number bed
I think this goes right back to the parent's point.

I presume you personally could set that up. I probably could too. But 99% of the world isn't tech experts and can't do that. Or fix it if something goes wrong. Even if you can, you might just want to go to bed and not have to debug a broken assistant integration first.

The benefit of cloud integration, for that 99%, is that there is a professional out there to keep it working.

ufmace··on Car dealerships revert to pens and paper after cyberattacks on software provider
That probably is the better way to see it at this point. There's already enough bad actors out there that it's not really worth keeping track.

I'd be willing to bet that they have comprehensively sloppy and terrible infosec practices and that we'll never hear any details about it - most of their customers wouldn't understand, and it would only expose how bad they are at all of this if they did.

ufmace··on Push Notification Fatigue Leads to LA County Health Department Data Breach
This, I find passkeys very difficult to understand.

It seems I can use my phone as my "passkey". Okay nice, that should mean I can use the same one on multiple devices, just like with a hardware Yubikey, right? Well apparently no. Use a phone as a passkey on one device for a web account, try to log into the same account on another device, using the phone passkey, and it doesn't work, claims there is no passkey. I can't see what passkeys are actually present on the phone, so I don't know what's wrong.

There's so many different ways to have and use passkeys, and no way to tell what the status is. I have no idea how the less-technical users are supposed to be able to figure this stuff out.

ufmace··on HH70, the first high-temperature superconducting Tokamak achieves first plasma
AFAIK it's not at all clear that solar and wind are really cheaper when making up a substantial part of a large-scale power grid that meets our current expectations of 100% consistent and reliable power everywhere, no matter what.

The unreliability of solar and wind requires either hot (constantly running and spinning) non-renewable backups or grid-scale power storage (has never been done so ? on cost to build and upkeep) to guarantee reliable voltage and AC frequency. The cost of that should be factored into determine the true cost of these power sources.

The stability of the grid is dependent on the collective physical inertia of the many tens of thousands of huge and heavy spinning turbine-generator sets that make up the majority of the current generating capacity. Most current solar power sources rely on grid-following inverters, which are not stable without a grid stabilized by a preponderance of large spinning turbines. There has been some work on grid-forming inverters that are less impacted by this, but AFAIK there aren't currently any that can replicate the grid stability provided by that physical inertia.

I'm less certain about wind turbines, but I think they have this problem too. I don't think they're controllable enough to be mechanically synced to the grid frequency.

I'd love to be wrong about this, please prove me so if you can! But I don't often hear these points addressed, and we're not helping anything by ignoring the complexity of the real world.

ufmace··on Allan McDonald refused to approve Challenger launch, exposed cover-up (2021)
That's the thing I always wonder about these things.

It's fun and easy to provide visibility into whoever called out an issue early when it does go on to cause a big failure. It gives a nice smug feeling to whoever called it out internally, the reporters who report it, and the readers in the general public who read the resulting story.

The actual important thing that we hardly ever get much visibility into is - how many potential failures were called out by how many people how many times. How many of those things went on to cause a big, or even small, failure, and how many were nothingburgers in the end. Without that, it's hard to say whether leaders were appropriately downplaying "chicken little" warnings to satisfy a market or political need, and got caught by one actually being a big deal, or whether they really did recklessly ignore a called-out legitimate risk. It's easy to say you should take everything seriously and over-analyze everything, but at some point you have to make a move, or you lose. You don't get nearly as much second-guessing when you spend too much time analyzing phantom risks and end up losing to your competitors.

ufmace··on PostgREST Tutorial: APIs made easy
I don't know much about Supabase honestly.

On concerns about testing etc. I can see letting automated testing, keeping a clean version control history, good architecture, etc slide at an early stage in the name of building fast. To me, that looks like building stuff in a more mainstream language and framework, but letting yourself be a little bit sloppy about those things. The difference is, the tools you are using don't actively preclude those things, so you keep the option open of adding them in later as needed, as gradually as makes sense. If you're building in one of these limited but all encompassing frameworks like PostgREST, sure you can probably go fast at first, as long as you're coloring within their lines, but as soon as you need something more or need to add some of that other stuff in, you hit a wall, and your only option is to do basically a complete rewrite.

ufmace··on PostgREST Tutorial: APIs made easy
The idea of PostgREST is cool, but I keep coming back to it not being very practical for most purposes.

It's slick when the default query API does everything you need. But it seems inevitable that you'll eventually need to do something it doesn't support well. Then you're building views and stored procedures. Okay, those can work, but version control, unit testing, composeability, etc just aren't at the level of any mainstream web framework. Not to mention logging, tracing, etc. The complexity is going to get unmanageable fast, and then what?

And the auth. It probably works okay with a few dozen users who are all trusted. Would you trust the Postgres auth system with tens of thousands of users, many of who are internet randos who may be malicious? It feels like a recipe for disaster.

But then if you're only supporting trusted users doing basic stuff, why not let them use a regular DB client rather than this API?

ufmace··on A ChatGPT mistake cost us $10k
I don't know Python or SQLAlchemy that great, though I do have the benefit of it being cut down to a small amount of code and being told there was a bug there. That said, I didn't see the actual bug, but I did mentally flag that as something I ought to look up how it actually behaved. It's suspicious that some columns used `default` with what looks like Python code while others used `server_default` with what appears to be strings that look more like database engine code. If I was actually responsible for this, I'd want to dig into why there is that difference and where and when that code actually runs.

It's also the case that "code review" covers a lot of things, from quickly skimming the code and saying eh, it's probably fine, to deeply reading and ensuring that you fully understand the behavior in all possible cases of every line of code. The latter is much more effective, but probably not nearly as common as it ought to be.

ufmace··on Make timelapses easily using FFmpeg
Probably true, but ffmpeg seems to have a ton of features too. It seems to me that CLI apps are inherently better at not distracting you with things you don't need. A CLI flag that you don't use is invisible outside of the man pages, not so for a menu or toolbar of a zillion options with names and icons you don't understand.
ufmace··on Make timelapses easily using FFmpeg
Davinci Resolve is actually the first thing that came to mind on the subject of, okay it's free, that's nice, but I can't for the life of me figure out how to do anything in it. I suppose it's not necessarily their fault that the search results for how to do basic things are garbage, but I guess an advantage of CLI apps is how-to results for them don't seem to attract nearly as much SEOified clickbait.
ufmace··on Make timelapses easily using FFmpeg
Nice, thanks! I tried using ffmpeg for a minor video editing task I had a few months ago - just a cut, crop, rescale, and volume adjust. I've tried a few of the mainstream GUI video editing tools, and IMO, they all have incomprehensible UIs, are way too bloated, and usually far too expensive for what I'm trying to do. FFmpeg may not be dead simple, but I find it much easier to skim the command line flag list to figure out how to do what I want. And once I do, I can save down a handful of useful sets of flags and refer to them next time. Cheers to ffmpeg, one of the kings of FOSS! If you ever feel the need to do any kind of video conversion or editing, definitely try to do it in ffmpeg first.
ufmace··on Romance author gets locked out of Google Docs for "inappropriate" content
I suppose it's already covered how the title is clickbait because the doc was blocked from being shared, not from being accessed. Also not described is exactly how "out there" the content was, how many people it was attempted to be shared with, was it shared to specific people or with an open-access link, was it ever accidentally or intentionally directly shared with anyone who might object to the content, and other things that could make this seem to be a very reasonable action.

Google may not always be great, but this sounds like a nothingburger until proven otherwise to me.

ufmace··on Install Asdf: One Runtime Manager to Rule All Dev Environments
Actually no, it manages the versions of the languages themselves, but doesn't interact with their package managers at all. The .tool-versions file it uses to mark the current version could be thought of as a lock file as well. It replaces (for Ruby) rbenv/rvm, not rubygems. Rustup, not Cargo, etc.
ufmace··on Install Asdf: One Runtime Manager to Rule All Dev Environments
I routinely work in Ruby, Python, Javascript, Java, Go, and Rust. The thing that drives me to use asdf is that without such a tool, every language needs a different version or installation manager and they all work slightly differently. It's a hassle to remember 6 different sets of commands for how to install a new version, check which version is active, switch to a different version, and to remember the slightly different quirks that each language's tool has. With asdf, they all work exactly the same. Granted that with Rust and Go it's usually less necessary to keep older versions around, but you definitely need it for Python and Ruby. Better to have all the languages work the same even if it's a bit more complex than needed for some.
ufmace··on The dangers of single line regular expressions
Seems to me this is more about the danger of passing anything derived from user input into the TEMPLATE side of a templating engine. Why in the world would you ever do that?!?

Obviously if you pass data into the variable side of the engine, you hardly have to worry about it at all, since it's already going into a place that was designed for handling arbitrary and possibly-hostile input and been battle-tested at doing it correctly in Production for many years. If you pass it into the template side, you're betting that you can be as good as dozens of templating engine writers working for a decade at doing that, in exchange for, well, I can't really think of any possible legitimate advantage for doing that.

ufmace··on I Lost Faith in Kagi
Thanks for that. After reading both, I'm fine with Kagi and somewhat more annoyed by the author.

Perhaps Vlad is a little excessively enthusiastic and protective of his baby. But then you don't do something frankly crazy like start a new search engine from scratch in 2023 without being a little bit off. If we actually want a viable alternative to the advertising-funded search monopolies, we've got to be tolerant of some personality quirks.

And perhaps the T-shirt gambit is a poor use of limited resources. But have any of the startups that ended up making it big not make a few poor investments on the way up? I'll forgive it.

Meanwhile, Vlad's response does spell out several ways in which this lori exaggerated or misinterpreted things. Which of course are not acknowledged or responded to at all, despite lori's self-important tone. If you want to take your ball and go home because somebody doesn't take your concerns seriously, well you can, but don't expect me to follow you.

IMO, Vlad would have been better-off making his response his own blog post somewhere rather than an e-mail exchange. But eh, at least it's out there.

ufmace··on The Towns Outsmarting Airbnb
> slight densification

I don't think this is seeing the issue the right way. Building sufficient housing to reduce the pure free-market price of temporary / hotel stays to a level where housing is still accessible to locals is likely to permanently change the character of many locations. Perhaps from a quiet mountain town to Disney World. IMO, the residents of such towns, and other potentially attractive locations, have the right to keep their community the way it is rather than be swamped by tourists and high-rises to house them.

It is likely better to regulate the short-term housing volume instead, such that the free-market price of that housing goes high enough to reduce the demand to a level that the community feels is consistent with maintaining its character.

ufmace··on I'm always rejected at airport e-gates– so the Office suggested changing my name
https://archive.is/WOhu8
ufmace··on The xz sshd backdoor rabbithole goes quite a bit deeper
Not seeing that as a point. It's probably not possible to have no performance hit whatsoever when you're checking the exact nanosecond count of every little thing. But usually nobody is doing that. It shouldn't be hard to not cause a substantial enough performance regression in SSHD logins that somebody who wasn't already monitoring that would notice and decide to dig into what's going on.

I'm not sure if it's been revealed yet what this thing actually does, but it seems like all it really needs to do is to check for some kind of special token in the auth request or check against another keypair.

ufmace··on The xz sshd backdoor rabbithole goes quite a bit deeper
The weird thing about this one is how it seems super professional in some ways, and rather amateur in others. Professional in the sense of spending a long time building up an identity that seemed trustworthy enough to be made maintainer of an important package, of probably involving multiple people in social manipulation attacks, of not leaking the true identity and source of the attack, and the sophistication and obfuscation techniques used. Yet also a bit amateur-ish in the bugs and performance regressions that slipped out into production versions.

I'm not saying it's amateur-ish to have bugs. I'm saying, if this was developed by a highly competent state-sponsored organization, you'd think they would have developed the actual exploit and tested it heavily behind closed doors, fixing all of the bugs and ensuring there were no suspicion-creating performance regressions before any of it was submitted into a public project. If there was no performance regression, much higher chance this never would have been discovered at all.

ufmace··on Interview with a blind developer on how he works (2017)
Thanks, very interesting. Those samples sound like total gibberish to me. I'm a native english speaker, and if I really concentrate, I can sometimes pick out a word or two, maybe a phrase with the written text right there too. Maybe I could get to understanding speech that fast if I worked my way up to it.
ufmace··on Amazon ditches 'just walk out' checkouts at its grocery stores
> "Tease and Squeeze"

I for one like it

ufmace··on The Ethics of AI in Military Decision-Making: Unpacking Lavender and Its Impact
The topic may be relevant, but I'm doubtful we can have a calm and reasonable discussion of the technical issues and morality with a hot war ongoing and many hostages still in captivity. There are more than enough hotheads on both sides to poison any discussion, and I don't think @dang can fix that.
ufmace··on The xz attack shell script
You're not wrong, but IMO that isn't the real problem. The real problem is the combination of highly popular core open-source utilities with near-zero maintenance resources.

This was all possible because XZ, despite being effectively everywhere, has one actual part-time maintainer who had other things going on in his life. That also means that there's nowhere near enough resources to redo the build system to some more secure alternative. If they had, say, 10 enthusiastic and skilled volunteer contributors with plenty of free time, they could do that, but then a new person appearing out of nowhere with a few helpful commits would never have a chance at being made an official maintainer or sneaking sketchy tools and code past the other maintainers.

Not that I'm blaming XZ or the real maintainer. Clearly whoever was behind this was looking for the weakest link, and if it wasn't XZ, it would have been something else. The real problem is the culture.

So I guess what this really means is someone at a big corporation making Linux distros should audit their full dependency tree. Any tool in that tree that isn't actively maintained, say at least 3 long-time active contributors, they should take over one way or another - whether that's hiring the current maintainer as a full-time remote employee, offering to buy out the rights, or forking and running under their own team.

I'm not necessarily super thrilled with that, but I guess it's the world we live in now.

ufmace··on XZ Backdoor: Times, damned times, and scams
Probably worth considering here - if this was a state-sponsored attack, it's entirely possible (and exactly what I would do if I was running such a program) that there is one person or department actually writing the code and list messages etc, and another person or team who sits between that department and the internet and whose entire job is to ensure that everything that comes out from the development team takes place at actual times and with timestamps that are consistent with whatever story they're using for the project. Possibly even once in a while intentionally inserting a "mistake" to hint to investigators that the person's real location is another chosen place, which is also different from the real place where the project is being run.
← PreviousPage 9 of 34Next →