HNHacker News
TopNewBestAskShowJobs

ufmace

7,508 karma · joined February 28, 2013

submissionscomments
ufmace··on My son (9 yrs old) used plain JavaScript to make a game, and wants your feedback
Curious how you did deployment. On the one hand, giving him his own live server on the net seems cool, but that's a bunch more technologies to learn in order to deploy. On the other hand, seems like it would take away from the independence of the project to be like, nice work, I'll put this on the net for you.
ufmace··on Two decades after Enron's bankruptcy, the company is back as a crypto firm?
This article is a much better analysis than anything I'd seen before about the rise and fall of Enron. An attempt to really dig into how and why it appeared to be and felt like an unstoppable rocketship of brilliance at the time that damn near everyone bought into, not just a hurr durr it's a bunch of fraud take.

https://mattlakeman.org/2020/04/27/explaining-blaming-and-be...

ufmace··on Dear friend, you have built a Kubernetes
I suppose I can see how people are taking this piece that way, but I don't see it like that. It is snarky and ranty, which makes it hard to express or perceive nuance. They do explicitly acknowledge that "a single server can go a long way" though.

I think the real point, better expressed, is that if you find yourself building a system with like a third of the features of K8s but composed of hand-rolled scripts and random third-party tools kludged together, maybe you should have just bit the bullet and moved to K8s instead.

You probably shouldn't start your project on it unless you have a dedicated DevOps department maintaining your cluster for you, but don't be afraid to move to it if your needs start getting more complex.

ufmace··on Don’t look down on print debugging
What I mean here is, with print debugging, the setup is usually you have a run or test case that you start, spits out a bunch of text from the prints, and is complete in a second or two. With an interactive debugger, you often end up spending a while stepping around and through things and watching how data flows or changes. Then it can be a pain if you realize something was important after you stepped past it.

Granted, there's nothing really stopping you from using an interactive debugger with frequent short executions, but using print debugging seems to encourage it and interactive debuggers kind of discourage it.

ufmace··on Don’t look down on print debugging
Yeah it's a big enough pain point that I'm sure it's been done in at least some places. I'm not really sure it'd be worth the bother and memory consumption etc to set up though. Not when print is dead simple and works everywhere.

More like regular debuggers, it seems to me like it's something to set up only when print debugging just isn't getting the job done and you think you need something extra to help solve the problem.

ufmace··on Don’t look down on print debugging
I've used both print and proper debuggers plenty. I tend to lean on print debugging more these days. The thing about debuggers, in addition to often being a headache to set up, it usually seems tricky and time-consuming to get it to step to the lines you actually want to examine and skip the stuff you don't. And if you step past something but then later realize it was important, time to start over.

It's often faster and easier to set things up to run test cases fast and drop some prints around. Then if there's too much unimportant stuff or something else you want to check on, just switch around the prints and run it again.

ufmace··on Show HN: Android Dev Quest – A puzzle game solvable only using developer tools
This is pretty cool! I'm not sure if I'm the target audience since I have virtually no experience developing Android apps, but I'm giving it a try. It might be helpful to clarify that the intent is everything is solvable using the on-device developer tools, nothing needs an ADB desktop system connection.
ufmace··on Stop making me memorize the borrow checker
That I can agree with. I think Rust strikes a pretty good balance with it though. You can still do those things if you really need to, but it has to be marked `unsafe`. This bounds the unsafety to only the parts of the code that actually need it, allowing those parts to be examined more closely to ensure they actually are correct.
ufmace··on Stop making me memorize the borrow checker
I don't really agree with that interpretation. In my opinion and experience, it does not restrict architectural choices to the extent that it makes it difficult to develop greenfield projects. It's more that it rules out a relatively small subset of architectural choices which are arguably a bad idea anyways, as they do infact have flaws that may not be obvious at first but will lead to a lot of pain if the project grows above a certain size.
ufmace··on Stop making me memorize the borrow checker
I don't really agree with this. I'd phrase it more as, you have to learn to really understand what the borrow checker is trying to do and how it makes you architect your programs and consider that ahead of time. Once you understand that, you'll rarely have problems with the borrow checker. It does preclude significant chunks of styles and data structures often used in other languages though.
ufmace··on Mitigating IP spoofing against Tor
The article here is basically PR from the Tor project. I suspect most reader here would find this relatively high-level technical analysis of the attack more interesting:

https://delroth.net/posts/spoofed-mass-scan-abuse/

ufmace··on Trump wins presidency for second time
Why doesn't this apply both ways? Red voters in Blue states are just as likely to stay home because they think their votes won't count. And ditto the other point, Red voters in Red states may not feel like it's worth the bother to vote when they already know their state is going their way.
ufmace··on Hacking 700M Electronic Arts accounts
If you're already using Tor, what's the point of having a VPN too?
ufmace··on RCE Vulnerability in QBittorrent
I agree. Calling this a "RCE Vulnerability" is ridiculously exaggerated.

What's next, are we going to declare web browsers to have a "RCE Vulnerability" because they allow you to download programs from any site which may or may not be secure and then execute them?

Or, hey everyone, did you know that if you live in an authoritarian state, the Government can do bad things to you?

ufmace··on Dear CTO: it's not 2015 anymore
I feel like all of this is true, but represents the larger background forces. I think a big factor in why it's hitting relatively hard now is the Musk takeover of Twitter - he laid off a ton of engineers, and nothing much happened. I think that was a shock to much of Big Tech that most of their orgs are really feather-bedded with people who aren't actually doing much to support the core business.
ufmace··on Starship Flight 5: Launch and booster catch [video]
The whole design process for them is based around launches being expensive and taking a long time to plan. It will be very interesting to see what happens when the whole process gets used to launches being relatively cheap and frequent. No need to spend years making sure the design is perfect and will definitely last a long time if you can launch a new one in a week if you make a mistake.
ufmace··on Show HN: Dead man's switch without reliance on your infra
I'm not sure what value adding a DeadManService would have then. Probably simpler to just have the attorney's instructions say, "Hire a technical consultant to carry out the following:".
ufmace··on Some Automattic employees accept severance package offer
> You seem to never been in that shoe (from a country no one hires from).

Why do you say that? I do have sympathy for people in such countries and circumstances, but this isn't about that. It's about corporate compliance. For better or worse, corporations cannot just do something because it's a nice thing to do. They have to comply with the law in both the country they are based in and operate in, as well as in any country any prospective remote workers might be in.

I also never claimed to have any concrete knowledge. It's entirely possible they are doing everything correctly. I just find it odd that they are reportedly doing something that many companies do not do due to it being legally complex, and also their CEO is spouting off a bunch of unwise statements on public forums while being actively sued, which any sane corporate lawyer would strongly advise them not to do.

ufmace··on Some Automattic employees accept severance package offer
This actually makes me really suspicious about Automattic. Companies generally don't refuse to hire outside of certain countries just to be jerks, they do it because complying with international tax obligations while paying employees in dozens of countries is complex and expensive.

Given that, and the behavior we've seen from Matt and Automattic so far, what are the odds that they've actually got a bunch of really great international accountants and are doing everything correctly everywhere, versus they're just ignoring all of the tax laws and winging it, and are therefore at high risk of getting smacked down once the relevant authorities get wind of what's going on there?

ufmace··on WP Engine sent “cease and desist” letter to Automattic
That, and the whole thing about Matt M going on a scathing rant about how bad WPEngine supposedly is[0], supposedly because they don't support WP page revision control as well as he'd like. Seems a bit over-the-top and breathless to me.

I figure the whole thing is a corporate whine-fest over who makes more money from actually hosting Wordpress sites.

[0] https://wordpress.org/news/2024/09/wp-engine/

ufmace··on WP Engine sent “cease and desist” letter to Automattic
I run my own Wordpress server for a blog, and IMO it's basically fine if you use reasonable deployment management practices and don't install 500 random crap plugins and themes. The basic install is about as bulletproof as it gets in the mainstream web software business.

I don't particularly love PHP, but you don't need to touch it if you don't try to write any plugins. Yes, some of its practices are pretty wacky, like every plugin has full access to the filesystem and database to do basically anything, and the system expects to be able to update code files in place from web requests, but meh, just give it it's own $5 server and let it do its thing, and definitely be very careful which plugins you use and how you get them.

What you get in return for this is a perfectly fine CMS that anyone with basic computer skills can run. Yeah, static site generators are cool and all that from a tech expert's perspective, but nobody who isn't a tech expert can actually do anything with them, and oh, by the way, the ability to make any changes at all typically involves at the very least SSH access to the host server with full write permissions.

ufmace··on The EV evolution is going to take longer than we thought
Thanks for the perspective. I don't own an EV, but I have taken road trips in a friend's Tesla. My impression was that the supercharger network (at least in the Northeast US) is dense and reliable enough and the route planning software good enough that road trips basically anywhere in the region are reasonably practical, though you'll be spending much more time at superchargers than you would at gas stations in an ICE car and have less ability to choose any route you like. Interesting to know that that's actually the highest level of EV practicality and many other models are substantially worse.
ufmace··on Buy, Borrow, Die – Explained
Probably more like you own a large enough percentage of the company and have enough day-to-day control over it that actually trying to sell a significant amount of your stock could trigger other investors to panic, wondering if you have some secret information about how the company is about to fail rather than just wanting to buy another island or mega-yacht today.
ufmace··on A heck of a wild bug chase
IMO it's very understandable to not know about this sort of thing starting out. Everybody was new once, and it's much easier to get motivated to build cool stuff than to read about all the fine details of all of the technologies we're using. I say, go ahead and take the shortcuts and build some cool things in a maybe sloppy way as long as the traffic and stakes aren't too high. Then, once you've got something cool built, take some time every now and then to seek out and read about more of the details of some of the systems and tools you're using.
ufmace··on "We ran out of columns"
I've never actually set up CVS myself, so I suppose I can't accurately say how easy or not easy it is. The "nobody" might deserve an asterisk - I'm sure it's not literally not a single person, but it seems to be pretty rare in my impression. Nevertheless, AFAIK, the non-distributed nature seems pretty limiting.

In Git, I can just create a local repo for anything, and I don't have to decide where I want it. I could never push it anywhere, or push it to a private hosted repo to collaborate with a person or team, or push it to a public repo to open-source it, and change between any of those at any time. I don't think you can really do that with these hosted systems. You could spin up a local CVS server if you really wanted to, but if you later decided you wanted to open-source it on Sourceforge, don't you have to abandon the history and publish it there as-is?

ufmace··on RustPython: A Python Interpreter Written in Rust
A quick check on the contributors page shows ~8ish heavy contributors working over the course of 6 years and 13k commits. That's a good thing to check for any project you're thinking about integrating with IMO.

That said, my experience has been that adding business features in Rust apps is quite fast indeed!

ufmace··on "We ran out of columns"
I think a lot of people who've only learned programming in the last 10 years or so don't realize that Git, and even more so the large-scale popularity of Git, is actually pretty new. A lot of programming happened before Git was created, and before it became mature and popular enough to be the default for everyone.

Many of these earlier systems sound terrible and hacky to us, but they were the best that was available at the time. Systems to "lock" files you were working on were pretty common because basically nobody did merges well. Most of them were based on having a server to manage the whole thing too, so they were only really common in corporations and larger and more mature hobbyist teams - this was also before you could spin up a cloud server for most things with a few keystrokes and $5 a month. It's low-effort to spin up a local Git repo to track your work on a tiny personal project, but nobody's going to set up a CVS server for that.

Anybody remember Joel On Software's 12 Steps [0], written in the year 2000, 5 years before the Git project was started? Where "use source control" is Step 1? There's a reason why that's there - at the time it was written, source control was clunky and a pain in the ass to set up, so a lot of smaller companies or ones with less mature development teams never got around to it.

I may be getting a little "old man yells at clouds" here, but be really thankful that Git is FOSS, ubiquitous, works great for 98% of projects, and is superlatively awesome compared to everything that came before it.

[0] https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-s...

ufmace··on Physicists may now have a way to make element 120
The way this stuff seems to work, it doesn't make sense to go theory-first. We can spin up a bazillion theories about it, with no clue which if any are anywhere near true. We've got to just try it, gather experimental data, and see if we can build any more solidly-backed theories around that data.
ufmace··on Panic at the Job Market
Yup, that sounds about right.

I'd also note that one of the reasons I prefer doing such things in person is (in addition to not taking up too much of the candidate's free time) that if they misinterpreted something or are going off in the wrong direction or something, I can correct them right away instead of letting them waste a bunch of time. This also lets you see how they tend to interpret instructions and take criticism and corrections.

It's also IMO a failure mode for a candidate to get a simple task that should be done in 5-20 lines of simple code and try to build some over-complex super-modular and extensible thing for it, and resisting correction on it not needing to be that over-engineered.

ufmace··on Panic at the Job Market
We have a hour total per interviewer. The basic FizzBuzz is intentionally incredibly simple, no reason anyone qualified to be a full time software engineer should take more than 10 minutes to build it in a pre-set-up environment in their language of choice.
← PreviousPage 8 of 34Next →