I also love using `/loop` at work on combination with a PR maintenance skill, helps me push up changes initially and have a session automatically monitor + fixup a branch to get it passing before I review it myself and then later send off for a human review.

Maybe a better metric: Across work + personal I have 1,000+ sessions in the last 30 days, longest session was 3d 20h

Running some `/stats` on my work computer shows for the last 30 days:

* Sessions: 341

* Active days: 21/30

* Longest session: 3d 20h 33m (Some large scale refactoring of types)

So I'm running a little over 10 sessions a day, each session varies from something like 1-2 hours to sometimes multiple days if it's a larger project. Running `/clear` actually doesn't start a new session fwiw, it will maintain the session but clear context, which explains why I can have a 3 day long session but I'm not actually using a single context window.

On the personal side I have activity in 30/30 of the last days (:yay); I've been learning game dev recently and use Claude a lot for helping digest documentation and learn about certain concepts as I try to build them in Unity. One of my more interesting use-cases is I have three skills I use during play tests:

* QA-Feedback: Takes random thoughts / feedback from me and writes to feedback markdown files

* Spec-Feedback: Loops every minute to grab a feedback item and spec out the intention / open questions

* Impl-Feedback: Loops every minute to grab a spec, clarify open questions with the user (me) first, then create an implementation plan

So I might have a friend play my game and I'll generate 20-30 items of feedback as I watch them play the game, things like minor bugs or mechanics in general. Over the course of the day my Claude will spec and plan out the feedback for me. I have remote sessions always on so I can use my phone to check in on the implementor job and answer open ended questions as they come up.

By the following day I'll usually have a bunch of plans ready for Claude to work on. I'll send agents off to do the simple ones throughout the day (bugs) and work with Claude on the bigger items.

Sorry for the long winded explanation but trying to convey the level of usage I have w/ Claude code. I do admit "thousands" is hyperbolic, as I'm probably only nearing 2k session hours in the most extreme months but I would say I on average use Claude every day to some capacity, often times both during work and after work (for my hobbies).

But I’m not necessarily oozing about it online — vocal minority and all.

I must be missing something or supremely lucky because I feel like I’ve never hit these “stupid” moments.

If I do, it’s probably because I forgot to switch off of haiku for some tiny side thing I was doing before going back to planning.

Modern models like Opus / Gemini 3 are great coding companions; they are perfectly capable of building clean code given the right context and prompt.

At the end of the day it’s the same rule of garbage in -> garbage out, if you don’t have the right context / skills / guidance you can easily end up with bad code as you could with good code.

It's so fast in fact that we just added `ty check` to our pre-commit hooks where MyPy previously had runtimes of 150+ seconds _and_ a mess of bugs around their caching.

Personally, I've found that the paradigm of "sharp knives in the drawer" can lead to some pretty nasty output from LLMs; it's felt to me like the higher the ambiguity the higher the variance in quality.

This has shifted my approach to A&D:

* Always enforce strict contracts, i.e. the ONLY way to do X is through Y.

* Fail loudly and fail often, assumptions and fallbacks only encourage AI to make larger assumptions.

* Boring is better, the less magic you implement the easier it is for LLMs to understand and extend.

Anyone else have some nuggets of truth they'd want to share as it pertains to A&D + AI?

Comments URL: https://news.ycombinator.com/item?id=45916354

Points: 1

# Comments: 1

[1] https://github.com/obra/superpowers

For example I work on a python codebase shared by 300+ engineers for a popular unicorn. Typing is an extremely important part of enforcing our contracts between teams within the same repository. For better or for worse, python will likely remain the primary language of the company stack.

Should the founder have chosen a better language during their pre-revenue days? Maybe, but at the same time I think the founder chose wisely -- they just needed something that was _quick_ (Django) and capable of slapping features / ecosystem packages on top of to get the job done.

For every successful company built on a shaky dynamic language, there's probably x10 more companies that failed on top of a perfect and scalable stack using static languages.

I've worked on large python codebases for large companies for the last ~6 years of my career; types have been the single biggest boon to developer productivity and error reduction on these codebases.

Just having to THINK about types eliminates so many opportunities for errors, and if your type is too complex to express it's _usually_ a code smell; most often these situations can be re-written in a more sane albeit slightly verbose fashion, rather than using the more "custom" typing features.

No one gets points for writing "magical" code in large organizations, and typing makes sure of this. There's absolutely nothing wrong with writing "boring" python.

Could we have accomplished this by simply having used a different language from the beginning? Absolutely, but often times that's not a option for a company with a mature stack.

TL;DR -- Typing in python is an exception tool to scale your engineering organization on a code-base.

I try starting my morning with learning, lately having a podcast to listen to while I start my day has been awesome.

Works perfectly well for us, we don't handle any PI or CC details and clubs can connect their PP account to our platform for their registration / event management needs.

[1] https://embolt.app

Initially I didn’t mind it because my team focused on technical debt, but it pretty quickly turned sour. Having to scrape up “work” for the team of 6 engineers each morning to appear productive to management was dreadful

Not really the same since Claude didn’t deploy anything — but I WAS surprised at how well it tracked down the ingress issue to a cron job accidentally labeled as a web pod (and attempting to service http requests).

It actually prompted me to patch the cron itself but I don’t think I’m that bullish yet to let CC patch my cluster.

It makes sense on paper, if the service helps confirm legitimate reviews for you and convinces you to purchase said product, they should receive attribution revenue for helping generate the purchase.

The reality is much much messier though, because often times the people who award attribution revenue have a conflict of interest against any service that could even potentially expose bad practices happening on their marketplace.

I once worked for a popular deal site that developed a price tracking extension, a certain marketplace threatened to completely ban us from attribution revenue and we had to kill the extension over night despite our users loving it.

Secondly, LV is one of the most water efficient cities in the world. We recycle nearly all of our indoor water back into Lake Mead, and despite the city growing by 800K over the last 20 years we've reduced per-capita water consumption by 55% [2]

Our water crisis is a symptom of the water rights debate between the four states, not our over-consumption of water. You could actually eliminate the state of Nevada from the water crisis debate over the Colorado river and we wouldn't even make a _dent_ in the impact, it's the irrigated deserts of AZ and water intensive farming in CA that's the unsustainable piece (coming from a proud local who grew up in LV).

[1] https://knpr.org/norms-favorite-desert-trees

[2] https://www.lvvwd.com/conservation/measures/index.html?utm_s...

If you can't tell I'm a bit of a proud Las Vegas local having grown up here, so there's bias in my words.

[1] https://knpr.org/norms-favorite-desert-trees [2] https://lvgea.org/water/

We're offering online memberships, event management, and a member database packed with features. Membership management is a crowded space, but it's also a low-tech space with lots of sleeping giants not willing to iterate on their product.

It's been a really fun project so far and even more rewarding to see clubs using embolt for their daily operations.

[1] https://embolt.app