16 ms·
Good software knows when to stop
- theorchid 7mo agoOracle Database has now been renamed Oracle AI Database. But I think that in time, they will rename it back to Oracle Database. The hype will pass, but the AI will remain, and the name will no longer need to include the AI prefix. AI will just become the norm.
- ssaboum 7mo agonot exactly what we're asking of database, don't you think ?
- jayd16 7mo agoIronically, yeah kinda. In so far as fuzzy text search goes, vectorization works great. The generative part of the AI hype is getting in the way.
- righthand 7mo agoNeeds for actual survival and functionality do not out weigh needs for product manager promotions anymore.
- pocksuppet 7mo agoThe destructive forces (fire clearing deadwood) of the economy have been artificially suppressed for a long time. Most companies are zombie companies now. The US is an entire zombie economic zone.
- cindyllm 7mo ago[dead]
- thewebguyd 7mo agoThat's what happens when you have nearly a decade of ZIRP & QE. Money printer go brrrr.
- theorchid 7mo agoWe want to maintain the status quo in technology. We want databases to remain as they were five years ago. But for some reason, Oracle implemented AI into its database. Perhaps they surveyed their customers, and most of them supported this initiative. Perhaps they surveyed the wrong audience, and real database users do not want to see AI in them. Or maybe they made this decision to get more investment or because of the hype around AI. But the decision has been made. And if AI remains in databases after the AI hype, the next generation of developers will no longer know databases without AI. That's why I said it will become the norm. But that's just my guess. Unfortunately, I can't see the future. I don't know what it will actually be like in a few years.
- easton 7mo agoNot only that, but due to their pattern of putting letters after the version number the current version is Oracle AI Database "26ai". I skimmed the video and the presenters said "Oracle AI Database 26ai" multiple times without even a glint of self awareness on their face. They must've picked the only people on the team that could say that without laughing.
- kube-system 7mo agoThat never happened to JavaScript. It still has Java in the name long after the Java hype ended. We never went back to calling it LiveScript.
- benttoothpaste 7mo agoals: both fitting and terrifying name for that new utility...
- PTOB 7mo ago... slowly losing all functionality until, suddenly, death.
- Jackevansevo 7mo agoif I ran an OS upgrade and was greeted by something like this I'd immediately be swapping OS.
- layer8 7mo agoIt’s optimistic to assume that there’ll be any better options left.
- NoSalt 7mo agoWe need something similar to the Svalbard Global Seed Vault, to protect un-AI'd Linux distributions so that, in the event of an AI apocalypse, we will have access to clean operating systems.
- deleted 7mo ago[deleted]
- allemagne 7mo agohttps://archiveprogram.github.com/arctic-vault/ https://archiveprogram.github.com/arctic-vault/ Of course, any AI smart enough to apocalypse us would also know about these.
- dirkc 7mo agoI like the fictional way the article starts! When chatGPT first gained traction I imagined a future where I'm writing code using an agent, but spending most of my time trying to convince it that the code I want to write is indeed moral and not doing anything that's forbidden by it's creators.
- ssenssei 7mo agoI built a spotify music extractor called harmoni that helps you download your playlists and I feel I'm done. It does its job and it caters to both non-technicals and technical people alike.
- tambourine_man 7mo agoSpotify is a moving target, however. It may change its API, remove it completely, etc. I think you can only be truly done if you don’t rely on a third party.
- latexr 7mo ago> I think you can only be truly done if you don’t rely on a third party. On a third-party that changes. Making software for a specific hardware like a game console or a specific e-reader may still technically rely on a third-party but doesn’t carry the same risk and you can definitely say you’re done.
- john_strinlai 7mo ago>Ignore feature requests — don't build what users ask for; understand the underlying problem instead not quite in the same area, but this advice reminds me of blizzard and world of warcraft. for years and years, people requested a "classic" WoW (for non-players, the classic version is an almost bug-for-bug copy of the original 2004-2005 version of the game). for years and years, the reply from blizzard was "you think you want that, but you dont. trust us, you dont want that." they eventually caved and launched classic WoW to overwhelming success. some time later, in an interview, ion hazzikostas (the game director) and holly longdale (vice president & executive producer), admitted that they got WoW classic very wrong and that the people "really did know what they want". anyways, point being that sometimes the person putting in the feature request knows exactly what they want and they have a good idea. while your default mode might be (and perhaps should be) to ignore feature requests, it is worth recognizing that you may be doing so at your own loss. after all, you might not not be able to fully understand every underlying problem of every user of your product -- but you might understand how to code the feature that they asked for.
- bheadmaster 7mo agoSame with Old School RuneScape. Jagex thought they knew better than the players what the game should look like, and overhauled the whole game to the point it was unrecognizable. It took a massive loss of paying members to get them to finally release 2007 version of RuneScape back. Even now, OSRS has double the amount of players that RS3 has. Lol
- j_w 7mo agoThis isn't even true. OSRS was on life support with very few players for years until they started giving it updates. Turns out the 2007 version of the game was ROUGH for a lot of reasons - they picked the time because, IIRC, it was the most complete backup they had. OSRS has now had nearly a decade of consistent updates, a large team, and typically 10x the online player count of the "modern" game. The catch is that OSRS is not the 2007 version of the game, it's an alternative update timeline which broke off at the 2007 version of the game.
- DataDynamo 7mo agoSo uhm where can I get the 'als' command then? :P
- Esophagus4 7mo agoIt’s mostly hereditary.
- DataDynamo 7mo agoI should have added /s Yeah...
- Tossrock 7mo ago"To order, to govern, is to begin naming; when names proliferate it’s time to stop. If you know when to stop you’re in no danger."
- muppetman 7mo agoThis is why I love Sublime Text. It's so fast, it works so well. It isn't trying to be AI, it isn't trying to evolve until it can read email or issue SSL certs via ACME. It's focused on one thing and it does it extremely, extremely well.
- deafpolygon 7mo agothis is why i am still on vim
- dgxyz 7mo agoYeah that. Same here.
- muppetman 7mo agoHa yes, learning vim was one of the best things I ever did. I can SSH onto a Juniper router and fix up config using vi. I still try to instill in juniors these days "Learn vim!" but everyone just wants to use nano (which I understand but nano isn't preinstalled on many network devices)
- computerfriend 7mo ago> everyone just wants to use nano (which I understand I do not understand. I have a very capable colleague/friend who uses nano. Unix hacker type, so I think it is what he is used to from growing up. I still find it strange, but such is the nature of preference.
- small_scombrus 7mo agoNano not powerful, but it is friendly, it shows you its keybinds. Vim is very powerful, but also very unfriendly. The difference in effort required to pick up Nano vs Vim is HUGE
- HoldOnAMinute 7mo agoI am still on "vi"
- rglover 7mo agoIt's not about software, it's about money. They're chasing what they see making money and being mimetic. Simple as. It's a shame and sad to see so many get caught up in this, but it makes sense relative to where the world is at. People are desperate and this is what desperation manifest looks like.
- xg15 7mo agoGood software doesn't get you VC funding.
- grishka 7mo agoAs if VC funding is a good thing. Good software is made by individual people, nonprofits, or privately-owned entities.
- jasonlotito 7mo agoVC funding gets you paid, which is a good thing. Not getting paid is less good.
- grishka 7mo agoVC funding gets you enslaved. There's no such thing as free money.
- coffeefirst 7mo agoBut more and more, as a user, VC funding is a pretty good sign that either the product is shit or later will become shit. Which is great because it means whenever I can I should go with the underdogs and SMBs.
- latexr 7mo ago> VC funding gets you paid So does robbing a bank. But it’s far from the only option. Plenty of indie developers thrive without any VC funding, and I thank every one of them for it. VC funding is essentially a guarantee that if the software isn’t shit now, it’ll be in the future, and that the creators care more about the money than doing something good. Case in point, the deterioration of 1Password.
- smm11 7mo agoAnd AI.
- grishka 7mo ago
- grishka 7mo agoDefinitely that, a finite scope is good and finished software is beautiful. But also, most of the modern software is in what I call "eternal beta". The assumption that your users always have an internet connection creates a perverse incentive structure where "you can always ship an update", and in most cases there's one singular stream of updates so new features (that no one asked for btw) and bug fixes can't be decoupled. In case of web services like YouTube you don't get to choose the version you use at all.
- criddell 7mo agoI moved to Obsidian after Evernote increased their subscription prices beyond the point I could justify and I think Obsidian is heading down the same path Evernote did. They keep adding more and more features to it when I wish they would call it complete and move it into maintenance mode. For me, the turning point for Obsidian was their Canvas feature. That was a big move beyond the initial design of it being an excellent editor for a directory or markdown files that supported links and all the other cool things you can do with a basic directory of files and a few conventions. Nothing proprietary, nothing much beyond the directory of files aside from a preferences store. IMHO, Canvas and beyond should have been a new product. If Obsidian was open source I would have been tempted to fork it at that point.
- carlosjobim 7mo ago> beyond the point I could justify Your accountant was calling you at late hours asking you what the hell was going on with your note taking expenses?
- sowbug 7mo agoThe more stars my personal GitHub repos have, the more likely the project was something I cranked out over a weekend to scratch an itch, and then more or less abandoned because it was good enough -- maybe even perfect for that specific itch?
- sammy2255 7mo agoLink this to the Spotify product developers
- esafak 7mo agoGood example. Spotify today is noticeably worse.
- Esophagus4 7mo agoI switched to Apple Music last year because of that. Spotify now has promoted songs in playlists and that was enough for me to cancel. I will say the music discovery on Apple Music is lousy compared to Spotify, but oh well.
- Bullhorn9268 7mo agoI dislike spotify but weirdly enough I can never point out exactly what's so frustrating about it...
- emilbratt 7mo agoApp is slow. It plays music video content as default. Gui has many non interesting parts. I just want a list of albums and songs. I guess I just want it to be "boring but functional. :)
- internet_points 7mo agoand messaging etc. making it a social network
- Esophagus4 7mo agoAnd “commercially promoted” songs in playlists
- deleted 7mo ago[deleted]
- wenbin 7mo agoWe should normalize "finished" software products that stop feature creep and focus strictly on bug fixes and security updates. It takes real courage for a builder to say, "It’s good enough. It’s complete. It serves the core use cases well." If people want more features? Great, make it a separate product under a new brand. Evernote and Dropbox were perfect in 2012. Adding more features just to chase new user growth often comes at the expense of confusing the existing user base. Not good
- ryandrake 7mo agoThis is one of the biggest issues in software development: So few projects are willing to admit that they are finished. I can probably count on one hand how many software products I use every day that actually get better (or stay the same) on update. The vast majority of them peaked somewhere around v1.0, and are just getting worse every time the developer touches them.
- janalsncm 7mo agoI can understand the incentives for professional software. If you admit the software is done then management will question why they need you anymore. For OSS it’s more psychological: admitting you’re feature complete is cutting off the dopamine hit of building new things.
- deleted 7mo ago[deleted]
- paxys 7mo agoYou are basically describing all software ever shipped before webapps and online updates became a thing. Companies wrote software and sold them in boxes. You paid once and it was yours forever. You got exactly what was in the box, no more and no less. The company then shipped a new verson in a different box 1-3 years later. If you liked it enough, and wanted the new features, you bought the new box.
- wenbin 7mo ago
- rutuhffhbb 7mo ago> ready to upgrade your favorite Linux distribution and packages to their latest versions It is "their" distribution, to do with as they wish. If this would happen to your workstation, you are a fool, for not following release notes. I already jumped distros for several reasons, marketing BS was one of them. I do not need latest scam or flag of the month!
- amelius 7mo agoReally at this point we should stop making software as we know it, but create minimal tools that an LLM can use.
- smm11 7mo agoNo, all software grows until it gets email. Jamie told me that.
- al_borland 7mo agoI’m having flashbacks to the email client built into the Opera browser back in the day.
- river_otter 7mo agoIt's the wonderful part about OSS and 'mission-driven' projects. If the mission is not to make money, then a project is free to reject addons/etc that might be lucrative but not add value to the core of the product
- bob1029 7mo agoI think notepad.exe is the strongest example of this right now. The amount of hacking required to even be allowed to re-associate text files with that particular exe on Win11 was shocking to me. I get that windows is extremely hostile to its users as a general policy, but this one felt extra special.
- latexr 7mo ago> I think notepad.exe is the strongest example of this right now. It’s a strong bad example, i.e. an example of software with doesn’t know when to stop. https://blogs.windows.com/windows-insider/2026/01/21/notepad-and-paint-updates-begin-rolling-out-to-windows-insiders/ https://blogs.windows.com/windows-insider/2026/01/21/notepad... https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-20841 https://msrc.microsoft.com/update-guide/vulnerability/CVE-20...
- dpcx 7mo agoI notice at this time there are no comments about systemd. I figured there would be at least one comment about it and "it does not try to do everything".
- patcon 7mo agoMaybe good software is like a living thing? It grows and grows and eventually slows or grows too much and dies (cancer), but kinda sheds its top-heavy structure as its regrown anew from the best parts that survived the balanced cancer of growth? Just forks and forks and restarts. It's not the individual piece of softwares job (or its community's) to manage growing in the larger sense, just to eventually leave and pass on its best parts to the next thing
- lrakster 7mo agoJust like all organizations are naturally self-expanding and self-perpetuating. Same with all organizations building software. The natural pressure is to expand. It is hard to resist it.
- jasonjmcghee 7mo ago> `als` doesn't just show files. > It predicts which ones you meant. > It ranks them. > It understands you. This is so good I want to know whether someone generated this or wrote it by hand.
- lgas 7mo agoIf they did they learned writing from an LLM first.
- motoboi 7mo agoIn 2020 I became a full time Java developer, coming from a infrastructure role where I kind of dealt with Java code, but always as artifacts I managed in application servers and whatnot. So when I first started dealing with the actual code, it scared me that the standard json library was basically in maintenance mode for some years back then. The standard unit test framework and lot of other key pieces too. I interpreted that as “Java is dying”. But 6 years later I understand: they were are feature complete. And fast as hell, and god knows how many corner cases covered. They were in problem-solved, 1-in-a-billion-edge-cases-covered feature complete state. Not abandoned or neglected, patches are incorpored in days or hours. Just… stable. All is quiet now, they are used by millions, but remain stable. Not perfect, but their defects dependable by many. Their known bugs now features. But it seems that no one truly want that. We want the shiny things. We wrote the same frameworks in Java, then python the go then node the JavaScript the typescript. There must be something inherently human about changing and rewriting things. There is indeed change in the Java ecosystem, but people just choose another name and move on. JUnit, the battle tested unit testing framework, had a lot to learn from new ways of doing, like pytest. Instead of perturbing the stableness, they just choose another name, JUnit5 and moved on.
- 0x457 7mo agoI remember we made a switch to redis because java's memcached library was unmaintained. I made I joke that it's just feature-complete and cannot be improved upon, people chuckled, but we still did the switch.
- hunterpayne 7mo agoQuite a bit of risk telescoping there...because you had the source code to the memcached library so in the theoretical case you found a bug in mature code (how many times have you seen that?), you weren't SOL. So instead you switched to an entirely new system? If you were trying to minimize risk and cost, you did the opposite unless memcached was doing something else that was a problem.
- 0x457 7mo ago
- sidewndr46 7mo agoDon't forget the lifetime support subscription you bought for "ls" 2 years ago. It turns out the lifetime is for the lifetime of the software, not your lifetime.
- hollowonepl 7mo agoThis is an article Microsoft Windows, Office, Outlook and MS Teams developers and product managers should read, they continually break the working software only to come back regularly to what they have invented already, in the meantime annoying many who had to experience the experiments in between…
- 0cf8612b2e1e 7mo agoWhat’s worse is they keep rewriting working products. Except, someone gets bored or misses a deadline, so they release a half baked replacement missing features.
- lasgawe 7mo ago> Good software knows the purpose it serves, it does not try to do everything, it knows when to stop and what to improve. agree with this point. new developers should care about this.
- cwoolfe 7mo ago"know the role and place your software fits in" yes! Probably one of the most important lessons of my career. As a junior dev starting out, I had no idea how my software fit into the company's product let alone into the entire ecosystem of what was already available and open source. Now as a senior, I see juniors making the same mistake that naturally arises out of this: needlessly doing things that have already been done or re-inventing the wheel. And now that coding ability is a cheap commodity, product development, and knowing where you fit into the ecosystem becomes the main skillset.
- ericmcer 7mo agoStardew Valley is a great example of this, and that more is not always better. Specifically he rolled out a "cave" system with procedural dungeon generation where players could mine through walls and other advanced systems, then undid all of it and ended with ~30 static layouts and very simplistic interactions. The entire game feels like a demonstration that simple, predictable and repeatable interactions with software have more longevity than cutting edge dynamic systems.
- Gigachad 7mo agoStardew is an example of the opposite though? The dev has been loading more and more content via updates for 10 years now. There's so much late game content that would take a very long time to play all of. People are waiting for the devs new game to come out but he is still working on Stardew.
- pkilgore 7mo agoYeah, but if you vertically integrate you expand your target market, increase switching costs, and can charge rents, so everyone is trying to do it now.
- twitchard 7mo agoCoreutils gets updates regularly! https://gitweb.git.savannah.gnu.org/gitweb/?p=coreutils.git https://gitweb.git.savannah.gnu.org/gitweb/?p=coreutils.git Even `ls` gets news flags from time to time. I think "stopping" is great for software that people want to be stable (like `ls`) but lots of software (web frameworks, SaaS) people start using specifically because they want a stream of updates and they want their software to get better over time.
- collinfunk 7mo agoThe bar for adding new options, especially short options, is quite high for coreutils. We have a (likely outdated) page of rejected requests [1]. Some of the changes people have strong feelings about... [1] https://www.gnu.org/software/coreutils/rejected_requests.html https://www.gnu.org/software/coreutils/rejected_requests.htm...
- dcchambers 7mo agoI agree with this basically 100%. > Say no by default — every feature has a hidden cost: complexity, maintenance, edge cases AI-assisted development is blowing up this long-standing axiom in the software development world, and I am afraid it's a terrible thing. Just because you can do something, doesn't mean you should.
- twodave 7mo agoYeah, I've written about this before on this site. Incentives in software licensing have gotten really stupid since the Internet (and more importantly, since the typical user's bandwidth has increased enough to allow all software installation to happen totally online). Now, too many pieces of software are a revenue-extraction optimization problem instead of attempting to serve a space or solve a specific problem. There are great exceptions to this rule, even in paid software, where the authors are significantly poorer in exchange for producing better software. I imagine the authors of BeyondCompare or Magnet (for example) could have done a lot better financially for a while using a recurring license model. There are also really stupid applications of this rule, such as what has happened with AutoMapper and MediatR in the last year or so, where the only meaningful commits since going commercial are the bits that check your license and try to fool you into paying :/ It seems like this shouldn't be a problem. It often only takes one developer willing to make a sacrifice to make a particular class of software available that actually attempts to solve the problem and nothing more. But in reality what we see is over time those developers that did make a stand start to look out for themselves (which I have no problem with) and try to take what they can while they have market share. How do we find a way to live in a world where developers can build useful things and be rewarded for it while also preventing every piece of software from turning into shit? I'm not sure what the answer is.
- rambambram 7mo agoAlso from 37signals, somewhere in their first book they talked about the importance of 'evergreen' things people always want, things like 'the speed of software'. As a junior dev I didn't really get the point or thought it was not that important. I browsed further in the book looking for other gems of wisdom, and this 'speed'-thing only stuck in my head for the wrong reason, thinking it was a little obvious for such clear writers with a solid vision. Only 15 years later - now a couple of years back - I started to realize the importance of this. The apps on my smartphones seemed to get slower and slower by the year. The fast software experiences were a real joy amidst slow apps. I now have an appreciation for their opinion on 'evergreen' things like the speed of software.
- dguest 7mo agoI think Signal (the messenger) is an interesting example: by being free, open source, and privacy centered, there's automatically no room for ads and it's difficult to monetize. Also they have to be very careful adding new features for security reasons. The result: very few features. Which is exactly what I want.
- projektfu 7mo agoYet it has one feature I love (schedule send) which WhatsApp doesn't have, despite adding countless features I do not like or actively avoid (AI, channels)
- krasikra 7mo ago[dead]
- sarthakaggarwal 7mo agoThis resonates with AI coding tools. Claude Code doesn't know when to stop —it'll do 30 agentic loops for something that should have taken 3. The cost implications of a tool that doesn't know when it's done are brutal.
- jackfranklyn 7mo ago[flagged]
- dang 7mo agoWe've been getting complaints that your comments are LLM-generated or LLM-edited. I've suspended the account for the time being. Can you please email hn@ycombinator.com so we can clear this up and hopefully restore your account? If anyone's curious about what the (informal to date, probably soon to be formalized) rules are, we don't allow either generated comments [1] or AI-edited comments [2] on HN. We want commenters to write in their own voice. [1] https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=by%3Adang%20%22generated%20comments%22&sort=byDate&type=comment https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... [2] https://hn.algolia.com/?dateRange=all&page=0&prefix=false&query=by%3Adang%20%22own%20voice%22&sort=byDate&type=comment https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...
- analog31 7mo agoAt first glance, the thread title made me think this was going to be about the halting problem.
- deleted 7mo ago[deleted]
- groby_b 7mo ago"Good software knows when to stop, look at ls!" ls: usage: ls [-@ABCFGHILOPRSTUWXabcdefghiklmnopqrstuvwxy1%,] [--color=when] [-D format] [file ...] I don't think it knew when to stop.
- deleted 7mo ago[deleted]
- teddyh 7mo agoRelated: The growth of command line options, 1979-Present <https://danluu.com/cli-complexity/ https://danluu.com/cli-complexity/>
- jdejean 7mo agoI think it’s always worth it to consider feature requests from your users. Other comments here reference video games. This is nothing like video games. Video games have arbitrary constraints anyway and should be carefully crafted to preserve the vision. If you don’t like it, make a new game. Software’s constraints are not arbitrary, they are attached to specific use cases and any new feature that benefits any of those use cases should be considered. The real issue is when these companies (especially VC backed) add new features and BS that no user has ever asked for. Features that exclusively benefit the company’s bottom line or support some quiet pivot to a new audience leaving everyone else to the curb.
- samlinnfer 7mo agoRediscovering the Unix philosophy?
- bojle 7mo agoA great example of good software with this definition is bspwm. I've been using it for 7 years now, it's as complete as a software can get.
- overgard 7mo agoIf that ever happens to "ls" I'm tossing my computer out the window
- ookblah 7mo agoin enterprise none of this tends to hold true at all. you need to balance the optics of what people think they need vs what they actually need. a lot of times people with "we MUST have features XYZ to buy" and then when they actually get set up you see they use only 50% or less of the features. was it useless to build them? they wouldn't even consider you in the first place if you didn't tick the boxes for some higher up decision maker. probably applies more to people who are already bought in. you have that "luxury" at that point, buy in, cost to switch, etc.
- unselect5917 7mo agoThis reminds me of a line from REAMDE that I'll never forget. "Writers like having residences." The backstory is they hire two writers-in-residence, who keep making more work and excuses for more work for themselves... so they can continue having a residence. The same is true for writers of code, it turns out. So we bit twiddlers sometimes gin up excuses to change things, so we have an excuse to be employed and having a residence.
- salomonk_mur 7mo ago"We must make a full rewrite of our codebase to X architecture / Y language". How many times I've heard that...
- ozim 7mo agoGood software isn’t always „software that makes money”. Of course it is important to do stuff that doesn’t make money. But if your goal is to make money you need software that people will pay for and people will use 20% of features but each one person will use different 20% of the features.
- nishantjani10 7mo agoa lot of people need to read and understand the message here. Very, very well said!
- 9Mfhf34U 7mo agoGood blog posts know to stop before recommending books by a fascist.
- hk__2 7mo agoThe opinions on DHH on some subjects don’t invalidate his expertise on some other subjects. See also Musk or Ford.
- 9Mfhf34U 7mo agoGiven how extreme those opinions are, it does bring up questions on his judgement in general, and you can just not give money to him and instead buy and recommend other people's books. > expertise on some other subjects. See also Musk what expertise?
- badenglish 7mo agothe problem is that user interface does not belong to user
- rubyrfranklin2 7mo ago[dead]
- Frank_WolfPeake 7mo agoA lot of software problems seem to come from the assumption that more features automatically create more value. In practice, the opposite often happens, the moment a product stops being predictable, users start carrying cognitive load just to use it. The best tools I’ve used over the years feel almost boring in comparison, they solve the core problem, stop there, and stay out of the way.
- segmondy 7mo agoFolks are now optimizing for promotion and recognition. So there are endless thirsty developers ready to tear down a stable software so they can be recognized as the one that rebuilt it and made it "better" either for promotion at Work or recognition with the community.
- wrs 7mo agoOff topic, but… “For the oldest amongst us this kind of lessons came from 37Signals…books Rework and Getting Real”. So the “oldest among us” are what, 40?
- pmoati 7mo agoThe Getting Real philosophy aged remarkably well ! "Say no by default" is something I wish more open-source maintainers would internalize... Every feature you add is a feature you maintain forever and knowing where to draw the line is probably one of the hardest skill in software.