HNHacker News
TopNewBestAskShowJobs

yourapostasy

3,287 karma · joined October 3, 2011

submissionscomments
yourapostasy··on Twitter kills its San Francisco headquarters, will relocate to South Bay
> (and high rent is a kind of giant tax on all economic activity, raising prices in shops, restaurants, etc.)

I’ve long pointed out to conversation mates IRL that for a technological civilization like ours, shelter costs are a straight deadweight, Tsiolkovsky rocket equation cost upon the innovation throughput that is the civilization’s lifeblood. In the U.S., healthcare pricing policies are as well, but that’s a different conversation. Both are stranded capital that need unlocking towards increasing the technological development pace.

But most people with mortgages are trapped like a monkey’s fist around a fruit in a jar, by the siren song of house appreciation.

I’d rather have fusion, life extension, solar system colonization, mind uploads and AGI sooner than be “rich” in real estate.

yourapostasy··on A skeptic's first contact with Kubernetes
> ...just means YAML juggling.

Perhaps I'm missing something, but even the "YAML juggling" still seems to be in an immature stage. As an example, a problem I've been wrestling with recently where I could not find a solution with yq or other YAML wrangling tooling is the following.

Say I have a YAML fragment like this:

rules: - apiGroups: - rbac.authorization.k8s.io resources: -clusterroles verbs: - get - apiGroups: - rbac.authorization.k8s.io resources: -clusterroles verbs: - list

I want to condense it to this: rules: - apiGroups: - rbac.authorization.k8s.io resources: -clusterroles verbs: - get - list

More generally, I want to find the smallest most compact representation possible between the apiGroups, resources and verbs terms, combining everywhere possible. In the example, I combined the verbs, but the same combining can take place for the apiGroups and resources terms. This comes in really handy when cleaning up a litter trail of these constructs built from figuring out what resources to add to enable more complex Helm Chart installs (the iterative nature of that exercise is another rant in itself) in reasonably restrictive environments.

I resorted to writing a script to solve just this problem, but I keep thinking I must have missed some solution to this everyone else seems to have solved but me. Apparently the solution eludes my local K8S experts as well, because they condense it by hand, which I refuse to accept as the proper solution.

yourapostasy··on Texas woman gets 15 years for stealing $109M from Army to buy mansions, cars
I idly wondered what the stolen amount to years sentenced ratio was for Madoff, and using $65 billion stolen to 150 years sentenced, he was put away at a level of $433M per year sentenced. So Mello is put away at about a level of $7M per year sentenced.
yourapostasy··on The CrowdStrike file that broke everything was full of null characters?
> Of course, we also need to first start punishing individuals for intentionally causing harm through their decisions even if the harm was caused indirectly through other people.

Legal teams are way ahead of you here, by design. They’ve learned to factor out responsibility in such a diffuse manner the “indirectly” term loses nearly all its power the closer one gets to executive ranks and is a fig leaf when you reach C-levels and BoD levels. We couldn’t feasibly operate behemoth corporations otherwise in litigious environments.

I personally suspect we cannot enshrine earnestness and character as metrics and KPI’s, even indirectly. From personal experience selling into many client organizations and being able to watch them make some sausage, this is where leadership over managing becomes a key distinction, and organizational culture over a long period measured in generations of decisions and actions implemented by a group with mean workforce tenure measured in decades becomes one of the few reliable signals. Would love to hear others’ experiences and observations.

yourapostasy··on CRIU, a project to implement checkpoint/restore functionality for Linux
> ...I find myself wondering about the path not taken here.

Check out mainframes and Tandem systems for a peek at that path. Lots of support in those systems for the notion your application’s substrate might suddenly go poof, and you need it to recover from where it left off as instantaneously as possible.

It’s expensive.

yourapostasy··on CRIU, a project to implement checkpoint/restore functionality for Linux
Yeah, I’ve always held a soft spot for CRIU, but I don’t see it battle-tested enough to trust big, gnarly closed-source third-part vendor enterprise Java products to run under it. And if I’ve reduced an open source piece of kit’s execution footprint enough to trust it, I’d probably reach for Unikraft with checkpointing to a Persistent Volume before CRIU, which feels like early days of VMWare.

Hopefully though, my trepidation is wrong. What is the most complex piece of software others have run under CRIU in production, and for how long?

yourapostasy··on CRIU, a project to implement checkpoint/restore functionality for Linux
> A two-digit number of these devices was meant to form a cluster of sorts...

That embedded constraint is fascinating. With the benefit of 20/20 hindsight, given the same substrate constraint, what direction would you have taken? I was thinking along the lines of maybe a C/C++ state machine library.

yourapostasy··on Kubernetes attacked by patent troll Intellectual Ventures
Can someone please explain how the patent covers non-obvious work? This reads to me like tunneling with VPN's, and after we have so many on our hands, that one naturally reaches for sprinkling some conventions and automation on top. We were doing this in the late 90's by hand, and the connections were so expensive we didn't run up enough instances to warrant establishing conventions and writing the code to automate them, but it was obvious that was the direction once bandwidth prices got less insane. Just curious what I'm missing (as they wouldn't have put this suit forward if they didn't feel they had a very good shot at collecting, right?).
yourapostasy··on I found a 55 year old bug in the first Lunar Lander game
> How does that thought process even work?

As it was explained to me, it was territory marking/office politics. Editors back then were very powerful when it came to decisions on content. They did not take kindly to anyone explaining/telling them they had no control over any portion of the content.

> What did they think the code meant?

This gets interesting. They were told it was for the computers, but upon seeing high level language artifacts that looked vaguely like English words, they grabbed their red marking pens and leapt into action, absolutely certain they were in the right as they had always been in the past. This was at the very beginning. Later, it got more nuanced.

> What changes did they make, anyway?

Early incidents had stories of galleys using non-proportional font forced to change to proportional font simply due to aesthetics. Red pens changing the contents of PRINT statements (because it said "print", and that was their domain, right?). Even later with more lessons learned and nuances started to creep in, this was way before programmer fonts made the scene, and the typical goofs one would expect from manual transcription were rampant. The pipelines did not exist yet back then for a long time to take raw source code and dump them into the non-digital typesetting systems at the time, so it was all laboriously transcribed from printouts by non-technical staff.

> Did they learn to not touch math equations before?

Very little cross-pollination of editors experienced with math-heavy technical writing, and those overseeing print products popularizing BASIC programming. BYTE magazine was revolutionary at the time for realizing this, and even they had some gaffs from time to time.

yourapostasy··on I found a 55 year old bug in the first Lunar Lander game
Oy vey, "no chance" is putting it lightly.

A lot of this BASIC code had roots in the 1960's-70's. Back then, editors ruled the roost of print magazines where this code often showed up within, and in books of collections of code they especially ruled with an iron fist. There was little notion that source code had to be dropped in verbatim with absolutely zero changes, so editors would make "judicious" changes in the source code. They thought they were "helping" with "obvious" typographical and editorial decisions.

This lesson was slowly, painfully learned until material improvements across the industry started to take hold starting in the 1980's and realization that source code shouldn't be touched in print really began to permeate the print industry. Though sometimes I wonder if this dynamic spurred the rise of BBS' and helped loosen the stranglehold print media had upon source code distribution, and what an alternative timeline might have looked like if the ones in power in print media were more open to "outsiders" having absolute control over some portion of "their" content.

I learned all the above decades later after I first started playing around with coding as a child, from talking with a much older friend who rose up from within the print media world and saw what happened. When I was a child, with zero adult guidance, and only a handful of books from the school and community library about programming, it was a wonder I stuck with coding at all with the countless programs I typed in by hand from print media that were similarly riddled with errors, so your reminiscing brought back powerful memories.

yourapostasy··on Major cause of inflammatory bowel disease discovered
That is, shall we say, a champagne problem (a problem we want to experience). Mass life extension potentially unlocks compounding effects that can lead to some bootstrapping outcomes. Expertise can be deployed deeper and/or broader across more adjacent fields for ever increasing cross fertilization.
yourapostasy··on Texas poised to get own stock exchange – with less red tape than NYSE or Nasdaq
I sometimes wish there were Talmudic-like annotated regulations that discourse upon the history and context of each regulation, down to the precise punctuation mark, word, line when those granularities have meaning, so we don't have to hold these "what was the reason" conversations in public, and have more meaningful conversations over "with hindsight, was the original reason justified" to add to those annotations.
yourapostasy··on Encryption at Rest: Whose Threat Model Is It Anyway?
> Rewrite every software, so that every programs handle their own private keys ? Yeah, that's a nightmare, not gonna happen.

PCI 4.0 disallows using Full Disk Encryption to fulfill its encryption at rest requirements, because it demands a finer-grained encryption authorization model. For applications subject to PCI 4.0 compliance, my clients have to encrypt beyond the application level, and down to the service account level used by the application (most of these applications use multiple service accounts for representing teams that use the applications), with different files encrypted for different authorization groups.

There are very few enterprise scale solutions addressing this at the moment, and the stopgap I've seen is indeed the application teams are resorting to handling their own keys if the enterprise doesn't offer a finer-grained solution. The QSA's don't yet understand how seismic a shift this is, nor how inadequate the assumed authorization schema is for the many edge cases out there that will be unable to adopt the assumption a single key for a single group is sufficient to model all use cases. It will be a little messy until folks sort through the edge cases coming down the pike.

yourapostasy··on Ogma: Interpretable Symbolic General Problem-Solving Model
> This is very close to the hype of that era.

I'm too dense to grasp the site's mathematical propositions (I don't have the mathematical grounding to understand Borel algebra not to speak of Borel Hierarchies). So it was no wonder I had a lot of trouble discerning how what it proposes was materially different from expert systems, inductive logic systems, and Cyc. The associative memory layer seems to be picking up some lessons learned from Generative AI, but I'm not clear on that. It will be interesting to keep an eye on this project and where it takes us, and see if it makes more sense when someone comes along and dumbs it down for Blubs like me.

yourapostasy··on A man ordered to hide his boat painted the boat on his fence
The general rule of thumb I've personally observed (YMMV) with those who hold such absolutist externality related positions is they hold it right up to the minute that someone else much more powerful and deep-pocketed than they start unilaterally imposing externalities upon them. Your abbatoir example is a good one, and the other one I've seen in real life is when a Swift, Cargill or other similar mega-agribusiness setting up a CAFO feedlot next door.

The odor externality from the manure piles/lakes usually riles such characters right up, but that is the least of it. Even when the manure management challenges are properly mitigated (and there are no such CAFO feedlots that can mitigate to only 2-3 incidents per year, it is more like 20-30 per year for the average one), neighboring properties like your parent commentator's are adversely impacted with sharply increased pathogen and contaminants control in their groundwater. As rural properties like your parent poster's usually rely upon well water, this becomes a pretty acute issue for neighbors.

Fracking operations also are frequently very sloppy with their adverse impact upon groundwater, even though they are very diligent upon staying on their property. Redress that makes whole including judicial system interaction expenses is difficult, expensive even for single-digit liquid assets millionaires, and rare.

At the end of the day, this has many characteristics of a classic engineering modeling problem, subject to unperceived historical biases. People who hold absolutist property rights interpretations like your parent poster are generally historically biased to a time period when such interpretations were couched in an energy-poor and population-sparse time of our civilization. Back then, as long as one was within approximately human- and animal-power scales of energy over the generational time span, and rural population densities, externalities from large scaling scenarios were rare for most people, and mostly theoretical. With our current access to energy and ability to rapidly densify neighboring properties, the available externalities to present materially change, and the interpretations (which are actually the mental models we work with) break down in the face of a engineering-like scaling step change that requires categorically different solution spaces.

I'm personally very sympathetic to your parent poster's position, but realistically, my personal experience has informed me of the dynamic I've shared, and I've since substantially modified my position.

yourapostasy··on A man ordered to hide his boat painted the boat on his fence
A lot of my friends who in their younger years held this position rapidly backpedaled after they added babies to their homes. There are very effective sound mitigation solutions available though, if you're willing and able to afford to remodel the room(s) you want to defend against such external sounds.

I interpret such actions as what to normally expect in a lower trust society and culture. We pay for such settings in many different ways.

yourapostasy··on Big data is dead (2023)
> ...managing that "proper ACL" that doesn't fit your business is a hell of a problem that nobody will get right...

I'm not sure there is a way to get this right unless there is a programmatic integration into the org chart, and ability to describe and parse in a declarative language the organizational rules of who has access to what, when, under what auth, etc. It has otherwise been for me an exercise in watching massive amounts of toil manually interpreting between the SOT of the org chart and all the other applications mediated by many manual approval policies and procedures. And at every client I've posed this to, I've always been denied that programmatic access for integration.

A lot of sites try to avoid this by designing ACL's around certain activity or data domains because those are more stable than organizations, but this breaks down when you get to the fine-grained levels of the ACL's so we get capped benefits from this approach.

I'd love to hear how others solve this in large (10K+ staff) organizations that frequently change around teams.

yourapostasy··on Open sourcing IBM's Granite code models
The inference engine Watson is still out there. Branding of IBM's Generative AI entry is branded watsonx [1]. Pushed aggressively internally, widespread high-impact production traction-driven cash gushing accounts remain elusive, but because it is a CEO focus story to sell to shareholders, it will remain protected until a critical mass of shareholders figure out the ground truth.

Unless the CEO can raise more debt and raid cash more than he has already by at least an order of magnitude, I'm puzzled how they even have the cash firepower to hire the right staff at the right scale and support them with the right infrastructure to compete with the current GenAI leaders, and IBM possibly might take the "package for enterprise" road instead of trying to beat everyone else to the bleeding edge. Not nearly as capable, but reliable enough in operation the lawyers and insurers can understand it enough to slap indemnity stuff all around it.

[1] https://www.ibm.com/watsonx

yourapostasy··on 3M executives convinced a scientist forever chemicals in human blood were safe
Indirection, responsibility splitting, and accountability factoring are enormously effective organizational tools that allow formal influence to be wielded within organizations through informal means that are legally impossible to prosecute in practical timeframes, and give broad cover to bad faith actors. We have adversarially evolved organizational behaviors that are possibly not solvable through purely legal means applied to post facto acts deliberately obscured through nerfed information retention policies, and the very structuring of responsibility, accountability, processes, policies, influence and so on might be fair game for some manner of more formal scrutiny.
yourapostasy··on Utah Locals Are Getting Cheap 10 Gbps Fiber Thanks to Local Governments
> money warps everything it touches.

I wonder what would happen if money transactions frame dragged transaction metadata along with the money. Today, the money is public data, but the far more interesting transactional metadata exchange is a hyper-fragmented market.

yourapostasy··on The Great Flattening
Perhaps marking a turn of Apple considering itself the center of an ecosystem to the center of the ecosystem, trapped within an echo chamber of its own hall of mirrors?
yourapostasy··on The Great Flattening
A flattening I’m watching with interest is the gradually increasing digital integration of the physical world. I’m hopeful that it opens the door to at least tap the brakes on the enshittification of our physical artifacts.

For example, there are landfill dumps-ful of mass produced electrical devices like shavers, toothbrushes, AirPods and so on tossed out for want of just a replacement battery made too difficult to replace by those mass consumers. But I’m seeing green shoots of hope in people leveraging the flattening by sharing how-to hacks to repair these, and in rare but hopefully increasing number of cases, improve them for longer service lives.

With gains in pushing CNC mills, wire EDM and more fabrication to small scales, big chunks of which are enabled by this flattening, I’m cautiously optimistic we will be able to distribute persisted, good engineering.

yourapostasy··on Unix and Multics (2019)
> If Multics had been treated as a research project rather than being a plan to invent a ton of new stuff and build a system that would be deployed in volume, everybody would be singing its praises today.

I wonder if Multics had to be pitched to funders as "a plan to invent a ton of new stuff and build a system that would be deployed in volume" to obtain the level of funding needed for it to prove out its precepts. As a research project, it might not have had the impact that it did upon modern OS theory, design and implementation.

Even today, there is an incredibly strong averse reaction by funding agents to the software notion of "build one to throw away".

yourapostasy··on I've forked neofetch to keep it alive
Did you get the number of commits off of the network graph? I use "git log" to pull the number of commits but had no idea the GitHub web site could count the number of commits between two repositories from the most recent commit of one of the repositories.
yourapostasy··on US Air Force awards $13B Doomsday plane contract to Sierra Nevada
Lest anyone think the December Air Force decision to eliminate Boeing from the competition was due to Boeing's ongoing leadership failures manifesting first as engineering and manufacturing quality issues, and now as real-dollar design and manufacturing contract eliminations, the rumored reason for the elimination was over contract issues, specifically data rights and fixed bid terms [1].

Would welcome HN'ers with more detailed insights into the data rights and fixed bid terms that were the bones of contention.

[1] https://www.reuters.com/business/aerospace-defense/boeing-el...

yourapostasy··on Why I Don't Invest in Real Estate
> What are we supposed to do about it?

This situation is a smaller economic stage upon which the same script is playing itself out on the larger economic stage. The FIRE economy [1] and its accompanying regulatory capture apparatus that enabled the pricing out of your and younger generations relies upon capturing the value derived from the network effects of aggregating people into the same volume of space over time. There are ways for non-accredited investor actors in this dynamic to get out from under the feedback loop, but they all take more time than most are willing to put in and in some scenarios, more trust within larger groups than is usually culturally feasible.

Some of the backlash is already inexorably unwinding in the baked-in demographic collapse in many areas of the world, but that will take at least a couple more decades to impact housing prices in a material manner (to within 2-3X median annual income). Mass population-scaled solution implementations are still currently quite out of reach, but you can see lots of people reacting with solutions that fit their individual profiles at the margins: intentional communities, co-operatives, vanlife, tiny home, etc.

Anyone who is not directly, daily working in the real estate industry should be commoditizing that complement of their lives, but the real estate industry has successfully convinced most to work for that industry with the "your home is an investment" canard...periodically (on average once every 7 years in the US)...with a ~10% round trip transaction fee after all is said and done (better than 2 and 20 in many scenarios per unit effort, however you want to measure it). Most people cannot stand against the allure of "your home went up in value!!!", but it's a clever trap.

[1] https://en.wikipedia.org/wiki/FIRE_economy

yourapostasy··on North Korean animation outsourcing for Amazon, HBO Max series
It will take awhile before regulatory requirements catch up and leverage technology that is already available today, but automated lineage capture of Relationship Bill Of Materials (RBOM) is already possible. We lack the data interchange standards and compliance compulsion to reify. That is in turn possibly due to regulatory and legislative capture? Other than the fleets of white shoe law firms that would be deployed against passage of such regulation, I do not know why structuring laws are in place for "trifling" $10K USD transfers, and not for these larger, more economically devastating cases of indirection.
yourapostasy··on Ant and the Grasshopper: Seasonality and the Invention of Agriculture
Gives a compelling reasoning and evidence of how agriculture was roughly simultaneously invented around the world.
yourapostasy··on Women Who Code Closing
Having sat on a board of a 501(c)(3) organization before, it does indeed sound like a collapse of funding for their operating model, which is unfortunate for such a worthy mission. I've always wondered how well US-based donation-funded organizations placed in such a situation would fare with the following pitch to their donors, and would like others who have sat on more such boards for most of their lives to help me understand why funding models are so aggressively donation-driven year-to-year such that it exposes them so much to economic headline risk: everyone is cognizant of the economic precarity facing us all, how about we ask for one last donation until the Federal Reserve declares we're out of the (next) recession, we'll go into hibernation if necessary (only filing paperwork to keep the organization alive on paper, with a static web presence, and responding to inquiries with unpaid volunteers), but we'll dollar cost average the donation funds into a broad market index fund as we go into this economic slowdown on a timetable you agree to, only perform a 2% Safe Withdrawal Rate, we'll survive through this together, and once we're officially out of the recession and a year past that, only then we'll go around shaking the tin can for donations again.
yourapostasy··on Women Who Code Closing
That's how I read it. Should be unsurprising in this tech economic environment and if some Fed watchers are correct, within the next 4-6 quarters, when the tech malaise extends to the general economic environment. When the cycle comes back in 6-10 years (unless generative AI sparks another dotcom burst sooner) and if there is demand for developers across the spectrum of experience again like the past cycle, expect these organizations to appear again.
← PreviousPage 4 of 34Next →