The least helpful possible framing for this, I think. Refusing to answer altogether has all of the risks of giving too high/low a salary, and none of the benefits of actual negotiation. If you're in a position where you can not answer, you're in a position there's no reason not to give them your desired salary up front and let them tell you why they can't do it. Pick a high number of course! If you're in a position where you can't afford not to answer, you should pick a reasonable number, and take whatever they give you, because you completely lack agency. This is the case where you might screw yourself out of money, but if you need the job that badly, do you really care? A better way to frame this, and this is always what I do if I have the agency to not answer, is to give them the number I'd like or remain mum, but either way when they make the final offer just ask them a simple question: "Is there any way you can come up a little bit from that?". If they say no, you decide based on that first number. But they'll almost always say yes, and you'll get a small effortless raise. I've done this about 10 times across my career and about 70-80% of the time I've gotten a bump in the 5-10% range. Which means that, collectively, about 30-40% of my current salary level is a result of that one question, applied consistently over time. You won't get a raise outside the salary band, but you might move from the median for that band up a notch or two within it, and that absolutely matters in the long run.
Yes perfect advice -- negotiate from a position of leverage and always ask for that little bump at the end. In my experience, not talking about salary early kind of sets everyone up to waste their time. One time it ended up with a full interview process that went very well for a job I thought would be perfect in an industry that _should_ have outstanding pay, and the resulting offer that was lower than my current role, paid hourly without benefits with a vague promise to later be an FTE; not only did we all waste our time, I was pretty upset about it. When I sent an email to the hiring manager they said "well you never told us your expectations" -- now the guy was dumb, he _knew_ I had a good job already, the comp he was offering was well below industry standard, and he knew my background, but nevertheless that is where a lot of hiring folks heads are at and it makes total sense: they want to get a good deal just like you do. Asking for salary band is good, especially earlier in your career, but to me it's now kind of irrelevant -- for the same reason you will go high, they will try to go low. I have a price I will be happy at, I say a number higher in the beginning but say depending on how everything goes there may end up being flexibility, and that I look at the entire package holistically. This is just to assess: "is it worth us continuing to engage". Not doing this would have wasted a colossal amount of time. I'm now in a position where I know where salaries generally are in different parts of the industry, and I can set a price based on what I expect and what my current role is, and I explain my reasoning. But yes: it depends so much on the situation. Benefits good? Growth potential at a startup good? Do I believe in the mission and that the founder won't abandon for an acquihire and tank my equity? Etc.
Funemployed right now joyously spending way way more time than 996, pulling the slot machine arm to get tokens, having a ball. But that's for personal pleasure. This post is receeding from the concerns about "token anxiety," about the addiction to tokens. This post is about work culture & late capitalism anxiety, about possible pressures & systems society might impose. I reflect a lot on AI doesn't reduce the work, it intensifies it . https://hbr.org/2026/02/ai-doesnt-reduce-work-it-intensifies-it The spirit of this really nails something core to me. We coders especially get help doing so much of menial now. Which means we spend a lot more time making intense analysis and critiques, are much more doing the hard thought work of 'is what we have here as good as it can be'. Finding new references or patterns to feed back into the AI to steer already working implementations towards better outcomes. And my heart tells me that corporations & work life as we know it are almost universally just really awful about supporting reflective contemplative work like this. Work wants output. It doesn't want you sit in a hammock and think about it. But increasingly I tell you the key to good successful software is Hammock Driven Development . It's time to use our brains more, in quiet reflection. https://github.com/matthiasn/talk-transcripts/blob/master/Hickey_Rich/HammockDrivenDev.md 996 sounds like garbage on its own, as a system of toil. But I also very much respect an idea of continuous work, one that also intersperses rest throughout the day. Doing some chores or going to the supermarket or playing with the kid can be an incredibly good way to let your preconscious sift through the big gnarly problems about. The response to the intensity of what we have, to me, speaks of a need to spread out the work, to de-concentrate it, to build in more than hammock time. I was on the fence about whether the traditional workday deserved to survive before AI hit, and my feels about it being a gross mismatch have massively intensified since. As I started my post with, I personally have a much more positive experience, with what yes feels like a token addiction. But it doesn't feel like an anxiety. It feels like the greatest most exciting adventure, far beyond what I had hoped for in life ever. This is wildly fun, going far far further out than I had ever hoped to get to see. I'm not "anxiously" pulling the lever arm on the token machine, I'm just thrilled to get to do it. To have time to reflect and decide, I have 3-8 things going at once (and probably double they back burnered but open, on Niri rows!) to let myself make slower decisions, to analyze, while keeping the things that can safely move forwards moving forwards. That also seems like something worker exploitative late capitalism is mostly hot garbage at too! Companies really try to reduce in flight activities. Sprint planning is about crafting deliberate work. But our freedom and agency here far outstrips these dusty old practices. It is anxiety inducing to be so powerful so capable & to have a bureaucracy that constraints and confines, that wants only narrow windows of our use. Also, shame on Tim Kellogg for not God damned linking the actual post he was citing. Garbagefire move. https://writing.nikunjk.com/p/token-anxiety https://news.ycombinator.com/item?id=47021136
I wish the author had stuck to the salient point about work/life balance instead of drifting into the gambling tangent, because the core message is actually more unsettling. With the tech job market being rough and AI tools making it so frictionless to produce real output, the line between work time and personal time is basically disappearing. To the bluesky poster's point: Pulling out a laptop at a party feels awkward for most; pulling out your phone to respond to claude barely registers. That’s what makes it dangerous: It's so easy to feel some sense of progress now. Even when you’re tired and burned out, you can still make progress by just sending off a quick message. The quality will, of course, slip over time; but far less than it did previously. Add in a weak labor market and people feel pressure to stay working all the time. Partly because everyone else is (and nobody wants to be at the bottom of the stack ranking), and partly because it’s easier than ever to avoid hitting a wall by just "one more message". Steve Yegge's point about AI vampires rings true to me: A lot of coworkers I’ve talked to feel burned out after just a few months of going hard with AI tools. Those same people are the ones working nights and weekends because "I can just have a back-and-forth with Claude while I'm watching a show now". The likely result is the usual pattern for increases in labor productivity. People who can’t keep up get pushed out, people who can keep up stay stuck grinding, and companies get to claim the increase in productivity while reducing expenses. Steve's suggestion for shorter workdays sound nice in theory, but I would bet significant amounts of money the 40-hour work week remains the standard for a long time to come.
Very similar to web3! On paper the web3 craze sounded very exciting: yes, I absolutely would love an alternate web of truly decentralized services. I've been pretty consistently skeptical of the crypto world, but with web3 I was really hoping to be wrong. What's wild is there was not a single, truly distributed, interesting/useful service at all to come out of all that hype. I spent a fair bit of time diving into the details of Ethereum and very quickly realized the "world computer" there (again, wonderful idea) wasn't really feasible for anything practical (I mean other than creating clever ways to scam people). Right now in the LLM space I see a lot of people focused on building old things in new ways. I've realized that not only do very few people work with local models (where they can hack around and customize more), a surprisingly small number of people write code that even calls an LLM through an API for some specific task that previously wasn't possible (regular ol'software build using calls to an LLM has loads of potential). It's still largely "can some variation on a chat bot do this thing I used to do for me". As a contrast, in the early web, plenty of people were hosting their own website, and messing around with all the basic tools available to see what novel thing they could create. I mean "Hamster Dance" was it's own sort of slop, but the first time you say it you engaged with it. Snarg.net still stands out as novel in it's experiments with "what is an interface".
↙ time adjusted for second-chance
Looks: A Halide Mark III Preview (lux.camera)
I'm the founder of both the Prosody and Snikket projects. Sorry about triggering alarms :) I can try to explain... Prosody is a popular choice of XMPP server software. It's used for all kinds of stuff, from self-hosted chat servers to powering Jitsi Meet, to Internet-of-Things applications. Prosody is extremely flexible, and has a bunch of configuration options that allow you to adapt it and extend it however you want. For some people, this is ideal. Those people should continue using Prosody. Snikket has a different scope. It is specifically an answer to a question like "How can I easily make a self-hosted WhatsApp/Signal for my family/friends using open-source software?" - Snikket contains Prosody, for the core chat part. But it's Prosody with a very specific configuration, and the configuration is part of the project, it's not intended to be modified by the person deploying Snikket. They only need to provide the domain name. - Snikket also includes additional components that a modern chat service needs. For example, it includes a STUN/TURN server to ensure that audio/video calls work reliably (again, preconfigured). - Snikket provides its own apps, which are tested and developed in sync with each other and with the server. This avoids the common problem of incompatibilities that occur when you have an open ecosystem such as XMPP, where different open-source project developers may develop features at different paces, leaving users to figure out which ones support which feature. It also solves the discoverability and decision fatigue for users (searching "Snikket" on an app store will get you an app that you know is compatible with your Snikket server, you don't have to go through a list of XMPP clients and figure out which one is suitable). - Snikket servers are not designed to be open public servers (these are an administrative nightmare). Instead, your server is closed and private by default. As the admin, you choose who signs up to your server by sending invitation links. The invitations also serve to simplify the account setup process - no need to prompt users to "choose a server", etc. They just need to provide a username. Projects such as Conversations differ by running a single public server (conversations.im) and guiding people to sign up on that server, or choose one of a long list of free public XMPP providers. In some cases that's all what you want. But onboarding a group of people that way is not fun (for example, they all have to share their addresses with the group add each other to their contact lists one-by-one - Snikket makes discovery of contacts within the same server automatic). Beyond these things, Snikket is all open-source and XMPP. But there is a focus on making a good polished and secure "product", if you like, rather than supporting the entire diverse XMPP ecosystem which includes a range of software of varying quality (weekend projects and more recently, 100% vibe-coded clients). For example, Snikket servers require certain security and authentication features which some older codebases that have fallen far behind modern XMPP standards (think Pidgin, etc.) simply don't support today. > it’s actually all based on prosody and conversations? As mentioned, I develop Prosody. I also collaborate with the Conversations developer and other XMPP projects. There's nothing shady here. The goal is just to make a best-in-class XMPP project that solves one particular use case (and it was primarily my own use case to begin with of course - I wanted to move my family off WhatsApp).
And what about the kids who get recruited for gang activity and do some pretty messed up stuff as kids? Should that not appear on a public record? This is where the problem lies, you essentially can only ever make it an all or nothing approach as it gets a lot harder to determine what should or shouldn't be apart of a public record. Especially since as you reflected in your comment, this becomes and opinion thing on whether someone thinks it matters or not what crime they did as a kid. The problem that is happening in most Western countries is that criminal organizations take advantage of the fact that minors get reduced sentenced and that their criminal records are usually kept sealed (unless tried as an adult). Whether it be having them steal cars, partake in organized shoplifting operations, muggings, gang activity, drug dealing, etc... Your reasoning for why this information shouldn't be public record seems to boil down to the fact that you don't agree with other peoples judgement of someone's past crimes. You'd like to see more forgiveness, and you don't think others will show the same forgiveness, so you want to take away all the access to information because of that. To me that seems like a view from a point of moral superiority. I'd rather people get access to this information and be able to use their own brains to determine whether they want that person working there. If you were involved in shoplifting at 17 years old, and turn 18, I think it would be very fair for a store owner to be able to use that information to judge you when making a hiring decision. To me it doesn't make sense that you turn a magical age of 18 and suddenly your past poor decisions vanish into a void.
 Top