yrizos
Joined 14 years ago
Karma
30
Submissions
43
Member since
May 12
Recent submissions
Comment · 10 months ago
Comment · 11 months ago
APIs need to stay stable even as the systems behind them keep changing. Each version becomes a contract that cannot move, while data models and requirements evolve around it.
Keeping everything working without slowing development is harder than it seems, and common approaches often break down once incremental changes start to accumulate.
Comment · 1 year ago
Thanks, glad it resonated.
I'm at that stage in my career where I don't code much anymore, so I don't really share the same anxieties younger developers have about Gen AI. That might partly explain my more optimistic view.
Comment · 4 years ago
Oh, I've heard it - a lot :) But it's probably not used as much anymore, it's been a long time since I last heard it.
Comment · 4 years ago
It's not uncommon for programmers - even for the great ones - to produce code that looks like it was written by non-programmers...
Comment · 9 years ago
There will be a data dump.
Comment · 9 years ago
That's not a useful metric. The questions that today show up as locked for historical significance were simply closed before the historical significance lock was introduced.
Conversely, the lock was introduced to stop those highly interesting (but ultimately useless) questions from getting deleted. If anything, it's a step in being less strict.
Comment · 14 years ago
Hey, "Why are there so few female programmers?" (http://programmers.stackexchange.com/questions/5780/why-are-...) is still an acceptable question, it's closed, but only because it's a dupe of "Career Prospects: Women at Management positions in Software" (http://programmers.stackexchange.com/questions/93462/career-...)
Also, while the community in the good old days was certainly vibrant, it wasn't huge, and it's not huge today either. But at least now we're steadily growing: http://www.quantcast.com/programmers.stackexchange.com
Lastly, I love how you say that the graphs don't include deletions, and one of them (supposedly) show deletions and undeletions. You kinda screwed up the queries there, the graphs don't make sense ;)
Comment · 14 years ago
It was closed and re-opened a few times (full revision history: http://programmers.stackexchange.com/posts/46716/revisions).
Every time that question got shared somewhere, it started getting crap answers instantly, everyone ignored the fantastic community curated top voted answer and went ahead and added yet another one liner saying "learn css".
No one wants that question closed, but at the same time only a handful of people actively prune it every now and then. Right now it's open, but if it starts generating crap answers yet again, we might close it. And then silently re-open it when no one's looking, hoping that the next troll that visits the site won't notice.
However, keep in mind closed doesn't mean dead, we have lots of great (but closed) questions (http://programmers.stackexchange.com/search?tab=votes&q=...), if at some point a question becomes incredibly troublesome, closing it is the easy - and reversible - fix. Killing crap answers, rewording the question to be a bit more specific, etc, is a very slow process, but it happens.
The goal was simple: help humans navigate complexity. Make domain experts and developers speak the same language.
We had no idea those same boundaries would matter for something else entirely.