Derrick Wippler

@ToughSf NGL, at first glance, I thought this was a satisfactory mod.

There's ~3 micrograms of Uranium dissolved in 1L of seawater. It represents up to 240 kJ of fission energy if fully consumed. It only takes about 10 kJ to desalinate 1L of seawater. A desalination-reactor can fuel itself on seawater with very wide margins.

@nikitabier @TeslaBoomerMama X = Customer Quality Control as a Service (TM)

@TeslaBoomerMama Good catch. Looks like we didn't cover reposts of subscriber-only content. Thanks - fixing.

I am subscribed to @elonmusk , why can I not see this?

@psviderski Here is my AI generated website for my mostly non AI generated project. 🤣 I've been using AI a lot more recently. I need to update the website, it does way more now. 😅 querator.io

Hey geeks, you’re so boring with your AI hot takes, predictions, and one-shots. I want to read about you building cool nerdy sh*t with taste again. Come back please! 🙏

@psviderski I've written this pattern enough, that I eventually wrote a library for this. My current version is called 'wait' (as in wait group) github.com/kapetan-io/tac… There is also 'run' which is used in Prometheus, among other services. github.com/oklog/run

A pattern I use in Go for running long-running services or background processes. The idea is that a service implements just one blocking Run(ctx) method that does all the busy work (serves requests, watches for changes, etc) To stop it, you cancel the context. This makes the interface very simple. If you need non-blocking start/stop, you build them on the spot where you need them: stop() -> just use context.WithCancel. The returned cancel() is your stop function. start() -> wrap Run(ctx) in a closure and run it as a goroutine. The caller owns the goroutine, not the service. It keeps the service itself clean and predictable. You can also add a 'done' channel to know when Run has fully returned for graceful shutdown. This shines when you need to manage many such services together. Run them as part of an errgroup and you get: - automatic cancellation of all services if one fails - a single Wait() for all of them to finish

@SophiaFioren @elonmusk @nikitabier I had a similar experience, but on a smaller scale x.com/nikitabier/sta… I posted about things I know about, once a day for a few months, I aborted the experiment when I realized there was no statistical improvement. I then cancelled my premium. No one will see this post.

Diabolic… I love this app

I never thought this day would come. Thanks to AI, we've hit the inversion point where TDD is something that actually saves time instead of wastes time. What a world we live in.

@DmitriyLeybel @ylecun @dandinohill Very embarrassing. Regan veto'd the bill intended to keep the doctrine, according to the Regan Library.

@ylecun @dandinohill The courts nullified it, and then the FCC removed it. Frankly, this monocausal explanation is embarrassing.

How did a country of 300 million mostly honest, hardworking people end up with so many corrupt people running its institutions?

@businessbarista Claude

I want to start a community dedicated to Claude Code. It’s become the gateway drug to coding and experiencing the power of AI for tons of people. This will be a space for people to share killer use cases, agentic workflows, proven prompts, and connect with other CC obsessives. Comment “Claude” if you want to join.

@kepano I ask claude to aggregate ideas using keyword search of my vault. Then collect all the thoughts into an idea doc. Then iterate from there into a final form.

if you're using Obsidian with Claude Code, tell me about your workflow, and what you've used it for

@_hacdan err, it's not on my X profile. :shrug:

@thrawn01 Why do I have your Birthday down as December 25th?

@thrawn01 Happy Birthday sir!

This from @obie captures how I'm feeling about coding agents

claude code needs an epilepsy warning

THIS, Since everyone else is on vacation, I get to be productive in peace, and it's so awesome. Not sure what that says about me though... 😅

I've been banned from @Reddit, and I have no idea why. 🤷‍♂️ I can still login, and see posts, even upvote, but there is a banner at the top of the site saying I've been banned! Seems like a coding error. 🤪

I agree! They will naturally - Focus on outcomes - Not be emotionally attached to the code - Care more about behavior than implementation - Throw away bad implementation faster thus speed up the learning cycle. Behavioral and Functional testing is even more relevant in the age of AI.

I wondered, which Programmer should I invoke instead of "you". So I asked Claude..... Answer: Rob Pike - ✅ Your preference for avoiding DRY in tests, inline structs, and removing "dead code" that can't be tested echoes Pike's famous Go proverbs: "A little copying is better than a little dependency" and "Clear is better than clever." - ✅ Functional/integration testing over unit testing - Your emphasis on testing public interfaces only, treating the system as end-users would, aligns with Pike's practical approach to testing real behavior rather than implementation details. - ✅ Pragmatic minimalism - "Avoid over-engineering," "don't add features beyond what was asked," and "three similar lines of code is better than a premature abstraction" could have come directly from Pike's talks. I think this explains my love of Golang and my admiration of ZIG.

> You think "speed vs. quality" is a cope for teams that are bad at both. If you have quality, then you are consistent, when you are consistent, you get speed. Consistency is the basis of quality, as you don't need to constantly reevaluate decisions you've already made, solutions you've already solved. Not having to remake the same decisions, you gain speed as you're not solving problems you've already solved. Work on solving the problems that -- when solved -- will be solved for the next 5 years, then don't solve it again The same can be said about focus, focus is about ignoring all the other good ideas and focusing only on the really great ideas. When you do that you get quality and speed as a result. It's a shame so few people understand this. Good luck on your adventure!

After Brex I had decided I didn’t want to start another company. But I found my calling. I’m starting another fintech company that can change the world. I wasn’t looking to startup another startup but this one was impossible not to. The opportunity is too big. But the problem is very technically, operationally, regulatory and financially complex. So I’m looking for a founding CTO that is interested in coming in this adventure with me. It’ll be hard, it’ll take long, but it’ll be worth it. Signs you’re a good fit: - You're a technical dictator, not a facilitator. Consensus is cosplay for avoiding accountability. - You've built systems where bugs mean lawsuits, not rollbacks - You believe big engineering teams are a symptom of bad architecture and weak leadership - You're obsessed with ontologies and data models. You know most systems are rotten at the core because engineers treat modeling as boring. - You optimize your own taxes, loans, and entities like it's a competitive sport. You think most people leave money on the table because they're lazy. - You've optimized your LLM setup obsessively. Engineers who use ChatGPT with default settings are bringing a mass knife to a gunfight. - You think "speed vs. quality" is a cope for teams that are bad at both. - Makes fun of 9-to-5 engineers that rest-and-vest - You have an extremely high bar for talent and still aim to be the best engineer on your team. Not secretly. Openly. - You believe the PM role exists because most engineers are lazy about understanding the problem. The best engineers make PMs redundant. The role is in person. In the Bay Area. All-day every day. If you’re interested, send me an email at: henrique@brex.com (we don’t have a name yet!)

We appear to be approaching a tipping point where the goal is no longer to make LLMS more capable, but to instead make them more efficient, while preserving their existing capabilities.