HN user

swells34

340 karma
Posts0
Comments138
View on HN
No posts found.

I wouldn't take this line of thinking too much to heart. At some point, a piece of technology is too complex for a person to parse what it means without sufficient background in this space. The "buzzwords" simply aren't buzzwords; you are using real words that accurately describe the project. People look at them, and either don't have sufficient knowledge to parse them in context, or are used to seeing them co-opted for use in low-effort marketing. I have some experience in this space (not a whole lot), and I was able to understand.

I like where you are going with the graphics in the readme; I'd spend some effort on creating "intended usecase" scenarios, scenarios that highlight situations where the project is the perfect fit. Using a few of these to highlight very different applications give people a good mental map of where this project would fit well for them.

"John is looking for a way to provide access to an internal tool to work-from-home colleagues. This isn't simple to do because [...]. Octelium is a good fit because [...]. Here is how John would set it up: [...]"

I doubt there is any specialised hardware on the Windows 95 machines, the specialised hardware is likely connected to something else.

Based on my experience with older government systems, this is likely an incorrect assumption. It was extremely popular in the 90s to create custom hardware that integrated directly to windows machines. I've had to reverse engineer so many drivers to upgrade old bespoke equipment to integrate with newer OSs

The focus here on "tariffs good vs tariffs bad" is missing the point. Tools can be used in a productive way or an unproductive way. I think anyone with even a basic understanding of global economics knew what the outcome would be when he started putting out blanket tariffs for no fucking reason, and the way he did it is objectively unproductive; we will live with the damage from this action for decades.

This is a good representation of my experience as well.

At the end of the day, this is because it isn't "writing code" in the sense that you or I do. It is a fancy regurgitation engine, that will output bits of stuff it's seen before that seem related to your question. LLMs are incredibly good at this, but that it also why you can never trust their output.

In my experience, complex tools encourage fluffy programming. You mention a generic container; if I were using C, I just wouldn't use a generic container; instead, I'd specify a few container types that handle what needs handled. If there seem to be too many types, then I immediately start thinking that I'm going down a bad architecture path, using too many, or too mixed, abstraction layers, or that I haven't broken down the problem correctly or fully.

The constraints of the tool are inherited in the program; if the constraints encourage better design, then the program will have a better design. You benefit from the language providing a path of least resistance that forces intentionality. That intentionality makes the code easier to reason about, and less likely to contain bugs.

You do pay for this by writing more boilerplate, and by occasionally having to do some dirty things with void pointers; but these will be the exception to the rule, and you'll focus on them more since they are so odd.

I used it quite a bit early on during military operations. The ability to see the timing component was key; not only would you plot the purchase locations, but you could play the timeframe of records, work out the timing so you knew the order in which they visited the locations, where they must have stopped for gas along the route. In a classic workflow, you'd then investigate the gas stations, attach them to the event with confidence intervals, pull CCTV footage, see if you can get a payment receipt, and enter all of that data back into palantir. A few days of doing this, and you can build up all a map of every aspect of the drug run; the who what when where and why. It's a fantastic organization system.

In the world of content moderation, we refer to this as constructive friction. if you make it too easy to do a thing, the quality of that thing goes down. Difficulty forces people to actually think about what they are writing, whether it is germaine and accurate. So generative AI, as you point out, removes all the friction, and you end up with bland soup.

Curious, could you not calibrate using a force sensor, then include the output as a learning parameter. This seams a naive approach, which likely means it has been tried early on with other low hanging fruit, but I'm curious what the analysis of that approach is. Is there a fundamental reason this wouldn't work?

I imagine the flight planning software they use was affected (so their ability to coordinate with other airport's ATC), but not their radio systems or aircraft radar (nearly all radar systems I've worked with are run on Linux, and are hardened to the Nth degree). Been out of the game for 12 years though, so things have likely changed.

I've run into #3 quite often in embedded Linux projects, especially when dealing with the Jetson ecosystem where upgrading to a modern Python is a nightmare due to all the specialized hardware. Glad to see I'm not the only one who runs into this.

I don't see it that way. Most of my travel (and what I assume is true for the majority) is that they are traveling to a location because of an event, be it work or personal. If I am delayed a day, then there is no longer any reason to travel, because I've missed the meeting or event. Every time this has occurred it is quite problematic.

Conversely, with a hotel, if they overbooked and I cannot stay there, there are usually quite a few locations nearby where I can get a room for a night. I've had this happen a few times and it's never been more than a minor inconvenience.

It would be silly not to first ask your interpretation, given that you are a college student.

Since this is about quantum computing, real world effects are very likely to be none except an exorbitant amount of grant money.

When trying to figure out something's type is the same as trying to fully comprehend a regex pattern, you know things have gone too far.

Well, it is average locally earned disposable income compared to local housing cost, as a percentage. And in that case, houses are ridiculously expensive now. Most of my prior generation relatives purchased homes in the 70s in their early 20s while working minimum wage jobs as single income households. They were forklift drivers and steel workers, required no education, yet somehow a house was cheaper than 2 years income. I think you need to question your understanding a little more thoroughly. Also look at how ridiculously cheap the average rent was... if you don't own, you rent, and rent was something like half of a paycheck, making saving for a house much easier.

And those low population areas carry low paying jobs, which are proportional to high population areas. Yes, we have a housing problem. For the average person on an average local income, a house is unaffordable. If you look back at the 70s, 80s, and 90s, houses cost many times more (before and after adjustment for local average income) now, regardless of where you look.

And religion in general is in a state of apostasy and is guilty of leading people away from reality. That's why it was invented after all, and it sure has done it's job. You'll never find a place more full of delusional self indulgence and aggrandizement than a church, regardless of which religion or denomination they subscribe to.

A majority of what you wrote is objectively false FUD. The only thing that I found accurate is: > it's getting more expensive and less efficient There have been a ridiculous number of medical advances in the last few years, advances that are actively improving and saving lives as I write this. Remember that time we had a pandemic, and quickly designed and produced a massive number of vaccines? Saved millions of lives, kept hundreds of millions from being bed ridden for weeks? The medical technology to design those vaccines, and to produce them at that speed and scale didn't exist 20 years ago. Cancer treatments, which you specifically mentioned, are entirely better than they were 10 years ago.

The actual issue, which is the only worthwhile thing you wrote about, is cost and availability.

Well, replacing novel creative functions with derivative creative functions. That's the big change I see here; similar to the difference between digitally editing an image vs. applying a stock sepia filter to it. Yes, we can use a model to regurgitate a mish mash of the data it was trained on, and that regurgitation might be novel in that nothing like that has been regurgitated before, but it will still be a regurgitation of pre-existing art. To some degree humans do this too, but the constraints are infinitely different.