3,287 karma · joined October 3, 2011
I want to see a GPT-based implementation of A Young Lady’s Illustrated Primer-like open world that constantly teaches. We have a lot of the precursors needed to attempt it and give it a shot.
Watch what they do, not what they say, I guess. Maybe it's mostly greenwashing?
The pandemic lockdowns were probably as close as we're ever going to get to observing how much a drastically reduced transport-intensive footprint is capable of helping the environment. If a lot of tension arises out of increasing RTO and shrinking labor pools, it will be interesting to watch how it resolves out.
When we replace Roombas with Moravec-class androids that perform common domestic chores, then I think we'll really be tackling the paradox. Right now I am guessing we're at the approximate equivalent of perhaps say, just before the early Cambrian Period, when vision systems started to show up in the fossil record.
So I'm hoping for an exponential development explosion that delivers androids that do laundry (sort, wash, fold, put up, identify for recycling), clean and prep food ingredients, dust/vacuum/mop/cleaning in general, return items to their places, make beds, take out and return rubbish and recycling bags and bins, etc. Even with a developed world income well above the 90th percentile, I cannot cost justify spending ~$0.5-1.0K USD for small slices of each of these capabilities with specialized equipment to automate them, which seems to be about the threshhold they're introduced at.
I saw this organically happen both pre- and post-pandemic. Pre-pandemic, it was rare if a Slack or email I sent to client staff was answered off hours. During the latter half of the pandemic and post-pandemic with those in WFH situations, it became much more common as staff learned to communicate all the time during brief idling periods while going about their off hours days and evenings. I'm going to miss this low-latency communication, but it is what it is.
If this is an actual secular trend instead of mere n=1 anecdata, then it will stack on the demographic trend baked in of ever-fewer workers for the next 20-odd years (assuming there is a baby boom in the next 3-4 years, which by current family and household formation statistical trends is still looking unlikely).
Mature code bases that haul in the bags of cash for a business in my experience tend to have more code handling the failure modes and edge cases than the path handling the successful execution. It can be a 90-10 split in cases where the business function is considered fully-automated (though of course that is actually an asymptotic, Platonic ideal). IMHO, too little is taught about coding for graceful failure recovery; it should be in the logical journey from TDD all the way through into devops. More often, what happens is this property is ad hoc accreted over time in code bases useful enough to stick around in production for a long enough time.
Developing world humans in their near-innumerable billions will always be economically (though arguably not organizationally nor for innovation-wise) cheaper than narrow automation for much "blue collar" work like this for as long as we leave Moravec's Paradox on the table, and not an evolving/improving science and engineering solution in the market.
Once I get into equipment to automate manual work (especially any commercial grade kit), I quickly discover the cost hurdle to clear is quite high. I either need lots of people I want to free up for another part of my business, or use the automation as close to around the clock as possible, or both before the capex and opex fall below the financial benefits. The ongoing maintenance of the new tool is a part that usually is not accurately accounted for in many people's opex calculations. I suspect this is why well-capitalized large companies are leveraging automation benefits sooner and we're seeing increasingly more emergent oligopolies, and Moravec-class automation when it ever arrives might be very profitable to the suppliers and disruptive to these incumbents.
It depends.
Usually it isn't the shell company itself per se that is expensive, it is the professional advice to use it to achieve your desired ends that you pay the big bucks for.
That said, a run of the mill offshore company in <insert-island-banking-nation-here> runs around $3-5K USD per year in various administrative and filing fees, depending upon your specifics.
Slightly less for a US shell company.
However. In order to avail yourself of advice for various tax minimization tactics and strategies, and have those tax attorneys nearly indemnify you when the IRS comes a-knockin'...now you're talking percentages of AUM. It isn't the specific consultation fees, though those are fairly healthy. These consultants won't really materially help you when the IRS audits you unless you have been running your entire bookkeeping and CPA book of business through them the entire time. Those fees rack up quickly over the years.
Once I worked out their business model and the numbers, it suddenly made sense why the fancy tax minimization strategies were commonly employed only by large companies hiring these folks, large companies with in-house teams like this, or count-the-commas-club UHNWI's. The strategies they shared with me were clever, years later I independently confirmed they would have worked, but I don't have nearly enough FCF to sanely justify using them.
Those who do reflexively apply probability assessments however, would do well to also perceive when to accept heuristic Good Enough solutions.
I've entertained the possibility that we might discover that "feelings" and language communication are emergent properties of statistical possibly partly stochastic nets similar to LLM's, and that the next tough scientific and engineering nut to crack is integrating multiple different models together into a larger whole, like logical deduction, logical inference and LLM's. LLM's are undoubtedly an NLP breakthrough, but I have difficulty imagining how its architecture can from using first principles as the training corpus derive troubleshooting steps to diagnose and repair an internal combustion engine, for example.
In the cases I've been personally involved with, it added significant costs to comply to move processing and storage onto Indian territory data centers that are run by large US corporate cloud vendors anyways. If you're large enough, it doesn't matter. If your use case serves a small enough long tail where it ends up on the wrong side of that added cost burden cutoff, then it matters. And I think that is unfortunate, because I see lots of Indian innovation happening inside that long tail, and such restrictions disadvantage the smaller scale efforts where the novel propositions seem particularly rich.
But perhaps I simply don't have sufficient data and perspective, so I'd welcome Indians closer to the action to help me understand why this is in India's interests. If I had to guess, I suspect the thinking is similar to China's: it is too strategic an area to give up, and India has enough population where it doesn't matter they are ring fenced into a walled garden as "only" the domestic market is big enough to stand within its own island market.
There is a larger technical culture and corporate political element with a strong undercurrent of budgets that has more to do with "products and innovate" at these non-BigTech companies, than someone from leading edge BigTech might be used to. BigTech companies also have such characteristics in most teams, but those leading edge teams due to incentives get all the public relations press internally and even externally.
Many of my non-BigTech clients have some full time staff who are plenty proficient in technical matters to seek BigTech employment. However, the rank and file staff of developers are almost invariably majority outsourced H1B's for budgetary reasons. This sets up a perverse incentive.
No matter how much the developers might agree with the advanced concepts promulgated by the full time staff developers, at the end of the day their outsourcing companies' contract renewals rely upon how many tasks assigned to them get "done" on time. And the project managers / scrum masters / etc. all the way up to and including middle management do not act upon the full-timers' advice (pretty basic, like build security and SRE in from the beginning) and encode it into the definition of "done" because they don't directly benefit from doing so.
There are ways to fix this situation, but they don't directly involve fancy tech or tech stacks.
That sounds like a Russian Federatiom Boomer generation dragging the rest of the nation down with it to rack and ruin for a nostalgic kick. For those on the ground in the Russian Federation or corresponding closely with those on the ground, is support for the war really mostly stemming from that generation and do they possess the kind of sociopolitical leverage as Boomers in the US?
It sounds overly simplistic to me to say, "lots of 60+ yr old Russians" are driving the support for the war. I'd be more inclined to subscribe to a description of an elite that control the levers of power and the economy are the drivers, and the general population like in too many nation-states (even the US, since objectively most legislation is passed by and for the elite) is more or less powerless.
See Moravec's Paradox [1].
[1] https://hackaday.com/2017/09/27/beamcnc-computer-controlled-...
It pretty much boils down to: it depends upon what the business wants to prioritize; operating margin or resiliency. There is an entire subfield investigating the statistical foundations of resiliency, and the general case of N-modular redundancy is in practice implemented as triple modular redundancy in most commercial systems that want to spend in this vector.
> Like it or not, these highly trained individuals are going to make mistakes every now and then.
Absolutely, and here is where the organization's no-blame learning culture swings into action for the well-led teams.
> It's a lot harder than it looks.
We all know this, and we can all help each other get better to deliver ever increasing value to our customers by sharing what works for the context we deployed within!
Of course, once you take advantage of such a representation at scale by deploying tremendously more complex infrastructures, you then have to deal with the dependency network meta challenge lest you inadvertently fall into dependency hell. While towards there lies NP-hard problems, they're still computable to a reasonable degree and I dare say a more robust situation than doing it all by hand like we do today.
The real challenge is the vast majority of devops staff today would really dislike reasoning about such a representation when it blows up in their faces, and I can't blame them for that kind of reaction.
It isn't mistaking, it is not prioritizing the cognitive load for the separation effort. When I was in Japan, I was impressed with the level of fastidious compliance I witnessed in materials separation. That convinced me the talk in the US about how mainstream households could not possibly support a comprehensive cradle-to-cradle materials handling infrastructure are really talking about culture and/or necessity and not logistics.
If you participate in a sport at a below world-class level where you get an opportunity to meet Olympians who teach clinics in that sport through learning by doing, take that chance because it is possibly the closest you will get to grasping just how wide the chasm is between you and "world class". In my case, the Olympians switched between roles on teams of amateurs they have never worked with before, then switched teams. All while teaching us the finer points of the sport, they would lead the team they were teaching to trounce the opposite team. It was seriously inspiring.
Definitely should have. However, it would have fell into the lap of the US to give the lion’s share and I remain unpersuaded the US had at that time the economic strength to pull that off without putting itself into an existentially compromising posture. Politically I doubt the Russian Federation would have consented to the kind of terms Germany and Japan did for the Marshall Plan and GARIOA respectively.
The Marshall plan was offered to and declined by the USSR, and they declined on behalf of USSR Eastern European satellites, so there were marketing hooks to revive a Marshall Plan. I wouldn’t be surprised to find out informal overtures were made for a similar plan and rebuffed by the Russian Federation; after all NATO membership was briefly and informally broached.
I suspect the Cold War wore out both opponents, and for the US it was a closer call than many admit today. Much like WW2 in the first half of US involvement was a pretty close call that was only admitted much later.
Might need to add the capex of equipment costs, and subtract the externalities costs of increases wear and tear on infrastructure and equipment.
For commercial or industrial work above a certain scale and complexity, you probably won't even be able to find a licensed electrician to validate work done by non-licensed personnel for sign off to send up to an inspector. I wouldn't consider a 1MW+ (or anything starting off with a 480V three-phase service) data center appropriate to install with non-licensed staff. There are gray areas the smaller and more residential scale you get. I've seen some pretty awful work funded by apartment complex flippers using non-licensed personnel, for example.
Once you are talking about common residential (anything less than 300A, where the average US house is usually around 100-200A, dual single-phase 110V service) though, it depends more upon finding a licensed electrician who agrees to a proposal to validate your work. This is not very popular because it is considered like a mechanic called in to inspect a shade tree mechanic's work or your relatives you only see around Christmas time proposing to pay you to inspect their attempt to clean up after a ransomware attack. But it does happen.
Assuming you can find and convince such a licensed electrician, you can do practically anything in such a residential context. It's a lot of work, and if you're a decent software engineer you aren't really saving much money. It would be the sort of thing to do if sloppy electrician work that doesn't meet the standards of r/wireporn or r/cableporn for example just drives you bonkers, and you happen to really like nerding out over strictly interpreting the intricacies of NFPA 70, National Electrical Code (NEC) with others, and you simply like having the satisfaction of knowing your electrical subsystem that well. If you squint hard enough, the NEC almost takes on a life of its own like source code, which appeals to a lot of technical types, so it isn't hard to find engineers and technicians of different stripes in aerospace, mechanical, civil, etc. doing this kind of DIY.
Code compliance inspections are required, but unless you are lighting up new service for example, enforcement varies pretty dramatically between locales. Again, I've seen some pretty shady disasters waiting to happen from flippers, but the city is none the wiser because no permits were pulled.
Add a mentorship role to their responsibilities where they oversee the operational maintenance of the code they write, with one iron rule: to promote the mentees' advancement, the clever coder is not ever able to further git commit to code they wrote until the mentee commits N number of changes to a chunk of code/documentation/tests they're trying to understand. The more operational the setting, even up to and including live production support at a call center, the better.
Clever code stops delivering benefits when the overall group/organization cannot support it in live operations under contracted SLA's. Clever, immature coders invariably go through a phase where they learn there is a giant step function change between coding for themselves or a tight knit peer group of clever coders and coding for an audience. Clever, mature coders expand their tooling way beyond coding to deliver for an audience. There are ways to effectively, operationally support clever code, but those solutions aren't just implemented in code.
It didn't use to be this way when our industry was orders of magnitude smaller, but the economics of the software industry nowadays has changed the dynamic. Our industrialization phase currently favors and rewards solutions at scale maintained by organizations larger than most tight-knit clever coder teams can sustain. Such clever teams are still critical for startups or insulated projects within larger organizations, but the price tag of monetization is this type of maturation.
These would be turn of the 20th century New York Jewish style bagels, made back then by bagel unions entirely by hand because the dough was too stiff for common kneading machines at that time (not quite sure how that squares with the giant industrial machines of the day, maybe the missing detail is the common bakery kneading machines were not up to the task though a hyper-expensive custom machine could be commissioned). These were so infamously toughly chewy they were hyperbolically touted as teeth breaking and taking an indecent amount of time to digest. "Food safe" because bagel bakery conditions at the turn of the 20th century are unacceptable these days.
Or maybe I've been bamboozled by food editors hunting for clicks.
When I build my own residence from scratch, I'm going for a more industrial loft aesthetic vibe where all utilities are run outside the walls where they are easily accessible to frequently modify them as I please. I want to be able to frequently update to code without making a giant, expensive mess, followed by a validation inspection from a licensed electrician. How we build residences today is not compatible with my desires for a sustainable, durable, maintenance- and repair-friendly implementation.
[1] https://en.wikipedia.org/wiki/Blindsight_(Watts_novel)#Major...
When cut open, they release a natural insect repellent. Works against many species of ants and cockroaches among other insects.
The wood is excellent material for fences. Very tough and durable.