Do or do not... there is no try.” ~Yoda
"Eight of Nine, Tertiary Adjunct of Unimatrix 01". Part of the Borg collective. Human translation: Yeah..I do software.
Tom Hanks shares the best advice he’s ever received
“Throw deep. If you’re gonna do it, do it”
“If you have the chance, do it. Don’t pause. If you’ve got an instinct, go at it”
@thecannalife420@ABrinkster@Bitcoin_Teddy Well massive inflation wouldn't really solve the problem. If anyone on social security couldn't afford anything, then it's equivalent to just stop sending them checks. i.e. bad things will happen.
@nadtokaai@naval So AI agents are going to hire humans to do laundry and clean your house? Wasn't the point that AI/robots were supposed to do the crap jobs?
As a senator tell me you either don't understand how SS is calculated (you should) or are misleading (i.e. lying to) the public about a narrative you're trying to push. TIP: SS is calculated from wages not assets. A billionaire doesn't pay themselves a billion dollars per year.
Murray: Is it true that people making under $184,000 pay a 12.4% Social Security tax rate?
Dahl: Yes
Murray: And the rate for someone making $1,000,000?
Dahl: 2.2%
Murray: So, a 12.4% tax for people making less than $184,000, but 2.2% for a millionaire or .0002% for billionaires.
@ABrinkster@Bitcoin_Teddy >Pay out those who have paid in and phase it out Worth understanding how it's currently financed. You'll realize why this might be next to impossible, or maybe you have a suggestion on how to pay out every single US worker past and present (who's paid in SS).
Corporation: "We made $4B but spent $3.9B so we only owe taxes on $100M."
Government: "Totally reasonable."
You: "I made $60K but spent $58K on survival."
Government: "You owe taxes on $60K."
You: "That's not—"
Government: "File by May 15."
The Oklahoma Panhandle exists because Texas chose to preserve its status as a slave state.
Under the Missouri Compromise, slavery was banned in territories north of the 36°30′ parallel. When Texas joined the United States as a slave state in 1845, its northern border was set at that line. Although Texas claimed land farther north based on earlier Spanish and Mexican boundaries, keeping that territory would have created a conflict over slavery restrictions. As part of the Compromise of 1850, Texas surrendered the strip of land north of 36°30′—the area that would eventually become the Oklahoma Panhandle.
The cession left the region outside the borders of any organized state or territory. Since it belonged to neither Texas, Kansas, New Mexico, nor Colorado, it remained a patch of unorganized federal land.
For roughly four decades, from 1850 to 1890, the area was widely known as “No Man’s Land,” a place with no formal territorial government, limited law enforcement, and an uncertain legal status. It was eventually attached to Oklahoma Territory and became part of the state of Oklahoma when Oklahoma entered the Union in 1907.
I've been coding for 40 years. Here are the top 5 things I wish I knew when I started.
1. 90% of the job is debugging and fixing, not creating new code. Which is still fun if you're good at it.
I used to think programming was mostly writing fresh, clever stuff. In reality, most of your time is spent in other people's (or your own past self's) messy code, chasing down why something that "should" work doesn't. Get really good at debugging early. Learn assembly reading, call stacks, and kernel debuggers. It pays off hugely. The best engineers I saw were absolute magicians at this.
2. Manage complexity from day one (ie: don't write slop and "fix it later" if it goes somewhere).
Very early on, I'd hammer out code and refactor afterward. Big mistake. Now I start with clean, skeletal structure (minimalism first) and flesh it out carefully, with AI or not.
Messy code compounds and becomes unfixable. Upfront discipline on architecture, naming, and simplicity saves enormous pain later, especially in large systems like Windows.
3. Tools and processes matter more than you think
We suffered with basic diff/manual deltas instead of modern source control like Git. Branching, testing, and good tooling would have made porting and collaboration way smoother. Invest in your environment, automation, and reproducible builds early. Good tools amplify your output; bad ones (or none) drag everything down.
4. Understand the problem and existing code deeply before writing
Don't jump straight to coding. Map out the problem, study what's already there (you'll inherit a lot), and plan. Low-level knowledge (hardware quirks, alignment issues on different architectures like MIPS/Alpha) was crucial. Also: assert early and often. It forces clarity.
5. People, politics, and "the right tool for the job" beat pure tech arguments.
Brilliant engineers still argue endlessly. Sometimes it's about ego, not merit. Learn to spot the difference and "steer" the conversation rather than "winning" it.
Bonus from experience: Side projects like Task Manager (started at home because I wanted the tool) can become your biggest hits. Ship small, useful things often. If you're just starting, focus on fundamentals, patterns over syntax, and building resilience for the long haul. It's going to be a wild ride, but the fundamentals still matter.
Listen up AI nerds: here’s the deal.
We need you to give 50% of your companies to the government and then pay a 50% unrealized capital gains tax on the rest. And then a 37% Federal Tax and a 13.3% California tax. And tip 30%.
And don’t let any of this affect your growth rates or shut your companies down.
We’ll need more money next year.
We’re spending $80B repaving the parking lots of every Learing Center in the country.
Greater good.