__turbobrew__

I believe that is correct.

I may be wrong, but last time I checked there was not a statically typed OTP implementation which is kindof a bummer. I think Gleam is the ideal implementation on top of the BEAM but it does just seem pretty immature.

The question is why do people feel bad about themselves? Everyone gets old, it is part of life. Why can we not accept that?

Why are so many people brainwashed to think baldness==bad? My hair really started to go down around 30 years old and am going to have to shave my head at some point, but who cares? Why does it matter?

I have experienced this several times lately when writing software with claude/codex. Sometimes vetting and steering the agent takes longer than it would have taken me if done manually. Sure you can just decide not to vet the output and go into full vibecode, but agents tend to do a lot of dumb things (such as not deleting unused private methods or having temporary variables that are not needed).

In my experience the most effective work pattern for me is using agents to perform research and feedback on high level design, then I write the code manually, then I ask the agent to review the code for potential bugs/issues and fix those. The agents have a much easier time making small changes once the design is 90% there without going fully off the rails and generating slop.

I am working on writing skills to make the agent better but it is a bit painstaking. For example I had to write this inside of a skill because sometimes the agent would just stub out methods and leave TODOs: “always fully complete the requested task before finishing edits unless input is needed”.

In British Columbia there is no special ed and there is no gifted program. It is a total train wreck. After the non-verbal autistic causes everyone to leave the classroom for the 5th time that day it gets really old (I’m not making this up).

I was a terrible student until high school — where I could start entering into college classes and/or skip classes — because the pace was too slow and I got bored and caused issues. Having the opportunity to do advanced classes was a huge gift for me and my peers I no longer disrupted.

I think it depends a lot on the operational maturity of the company. Some places are running the LGTM observability stack, sentry for error reporting, 24/7 on call rotations, playbooks for all alerts, etc. Those organizations will have less issues running systems like temporal because the operational framework is already there.

Other orgs have never heard of alerts or error reporting and naturally will not catch issues until they are catastrophic (for example services that crash frequently in the background go unnoticed until the crash frequency causes a catastrophic failure). In my experience a lot of issues are pretty simple such as running out of memory, CPU throttling, crashes caused by simple bugs (nil panics). If you have good observability you can catch those issues early.

For example: people rag on Ceph that their cluster somehow got into a broken state, but that really only occurs when abuse of the ceph cluster has went on long enough that the cluster finally reaches the tipping point where it is unrecoverable. If you set ceph up, follow the correct replication rules so components are spread across failure domains, and use the metrics and alerts that are distributed with ceph it is actually quite hard to break the cluster.

It is called “Buy, Borrow, Die” and it is a very real thing.

Also, if you are wealthy enough you can just wait out any economic downturn. Hell, Im not even that wealthy and it would have to get really bad before I would be forced to sell in a down market.

> In fact the conversion rate between them is about 20. A wealth tax of 1% is equivalent to an income tax of 20%.

Sure, but you actually have to work for continued income. Wealth accumulates with no input once established.

Wealth has the ability to increase (capital gains) without having to pay tax until it changes hands, whereas when income increases it is immediately taxed at a higher rate. Additionally, wealthy people can use securities as collateral for near zero interest lifetime loans which also bypass having to pay income tax.

This is the reason why I got a hybrid. Many of my trips are on routes that don’t have good charging access and charging is just too slow for the length of trips.

Also, I bought a rav4 hybrid which is one of the most common cars on the road here and therefore mechanics have a lot of experience working on these vehicles.

I have been thinking the same thing. I don’t want this turd in my index funds.

I think it is pretty common that devs have read only access to all source code.

The real question is why github has 3800 internal repos.

You speak very authoritatively on something you don’t know.

Hashing passwords has been a thing for at least 50 years now. V3 unix had /etc/passwd which hashed all user passwords. Notably, these hashed passwords in early unix have been cracked: https://arstechnica.com/information-technology/2019/10/forum...

I guess you got your answer.

My wife works in IT at a mid sized city. They still store credentials in source control.

You are calling infra teams green for using ceph but then recommending hand rolling a sharded system on top of nfs? I think you have it backwards.

> But there are services that are located here and only here and only here

Why is that? You would think the company ending events like IAM going poof due to it being dependent on us-east-1 would be top priority to fix?

What I have seen at other companies is that the older datacenters have suboptimal designs which are impossible to fix after the fact.

There are lots of people “trapped” in blue states too, if that is how you want to put it.

As a Canadian citizen, this is one of the things I envy about the USA the most: having 50 different choices. There is currently a lot of tension in Canada between provinces like Alberta and Quebec which want very different things but are bound by the same set of laws. In Canada you are given some choice regarding geography (although the vast majority of population lives within 100km of the southern border, so in reality if you want to live in a city there isn’t much choice), but very little choice when it comes to laws and general governance.

I personally would love to live in a western state like oregon, arizona, or new mexico where I feel like there is an appropriate balance between freedom, geography, and government for my lifestyle.

Unfortunately no. I made the jump in 2022 from doing on-prem at a small company to doing on-prem at a hyperscaler when software engineers were very in demand and got placed in an organization which does physical datacenter design and core software infrastructure (software defined networking, service discovery, host management, datacenter failovers).

Back in 2022 you could make the moves, but I think now it is very hard to make the jump.

Part of the issue with building and running very large on-prem infrastructure is that you can only get experience by doing it. It not like you can run thousands of racks in multiple datacenters as a personal side project.

The logically consistent explanation for both your experience and my experience is that you are on the other side of the K as people who are in demand and I am on the same side of the K as people in demand.

My guess is that one of the following applies: 1. You do not live silicon valley 2. You do not work at a FAANG 3. You have not built foundational infrastructure

I think if all three of the above are true, you are in demand to build AI hyperscalers. The trillions of dollars going into datacenters has to be built and managed by humans.

I don’t know if it exists already, but bazel would be very useful for the same type of MCP server. Since all dependencies are explicit you can pretty easily do a bazel (r)deps query to find related targets.

Not sure why you are being downvoted. This is my experience as well. If you have experience at FAANG doing “foundational work” (read: datacenter engineering, core software infrastructure, multi zone computing, point of presence management) you are still in high demand. Many of the people I know in such areas are going to the big hyperscalers to build the infrastructure to run AI inference. There are not a lot of people who have experience doing this stuff and that domain is in very high demand.

I had a similar experience (seeing blobs) where in my sleep I saw my baby boy conceived. A few days later my wife took a pregnancy test and it came back negative, I was majorly let down as I had this vision and strong feeling there was a baby.

A week later my wife misses her period and she is pregnant. It turns out my vision is more accurate than the 99% accurate pregnancy test.

I never had a similar vision since.

Just use chef or whatever configuration management system of choice.

> There's more evidence to support the earth will be wiped out by a meteor than their is evidence Apple will lock down their macOS hardware.

If you don’t think a for profit hardware company which also makes operating systems will never think about making it so only their software can run on their hardware, I don’t know what to say to you. They already do this with iphone/ios. It is possible they do with mac/osx. Im not saying it is guaranteed, I am saying it is possible. And I am also saying it is much more possible than a meteor wipes us out in my lifetime. If you disagree with that, fine.

I am pretty sure I will be vindicated by Asahi never being relevant.

Are you making the argument that an extinction level meteor event is within the same realm as Apple deciding to lock down their hardware? It is called risk management, here is how it goes: The likelyhood that an earth ending meteor comes and destroys the earth is very very low and therefore Debian decides that they should still write software. On the other hand the likelyhood that Apple -- a for profit company -- locks down their laptop hardware like they do for iOS is much higher. Apple has a history of walled gardens and conceivably there could be profit motives to lock down the hardware. Given the risk, potential supporters of Asahi have to decide whether or not it is worth the risk of putting a bunch of time and money into the project.

> I sit at the intersection of design, anthropology, and web development

How do these people still have jobs post ZIRP?

Sure, there is no legal issue with these contributions. The problem is why would a project like Debian spend a bunch of work stewarding the Asahi project when Apple can just make the project impossible to progress if they so desire? The Debian project already is strapped for resources to build their distribution and stewarding a possibly throw away project is probably not the best use of their time.