time to refactor the code base so this tumor can be deleted?
513 karma · joined August 15, 2007
The steep decline in the early months of 2023 actually started with the release of ChatGPT, which is 2022-11-30, and its gradually widening availability to (and awareness of) the public from that date. The plot clearly shows that cliff.
The gentle decline since 2016 does not invalidate this. Were it not for LLMs, the site's post rate would now probably be at around 5000 posts/day, not 300.
LLMs are to "blame" for eating all the trivial questions that would have gotten some nearly copy-pasted answer by some eager reputation points collector, or closed as a duplicate, which nets nobody any rep.
Stack Overflow is not a site for socializing. Do not mistake it for reddit. The "karma" does not mean "I hate you", it means "you haven't put the absolute minimum conceivable amount of effort into your question". This includes at least googling the question before you ask. If you haven't done that, you can't expect to impose on the free time of others.
SO has a learning curve. The site expects more from you than just to show up and start yapping. That is its nature. It is "different" because it must be. All other places don't have this expectation of quality. That is its value proposition.
And that is exactly why so many people gripe about SO being "toxic". They didn't present a well posed question. They thought it was for private tutoring, or socializing like on reddit.
All I can say to these is: Ma'am, this is a Wendy's.
They were unaware of or unwilling to follow the rules of the site. They mistook SO for reddit, a place for socializing.
If SO manages to stay online, it'll still be there for #2 people to present their problems. Don't underestimate the number of bored people still scouring the site for puzzles to solve.
SE Inc, the company, are trying all kinds of things to revitalize the site, in the service of ad revenue. They even introduced types of questions that are entirely exempt from moderation. Those posts feel literally like reddit or any other forum. Threaded discussions, no negative scores, ...
If SE Inc decides to call it quits and shut the place down and freeze it into a dataset, or sell it to some SEO company, that would be a loss.
"Asymptomatic" means you have a cold but you show none of the symptoms, hence a-symptom-atic, no symptoms.
This video is not about the entire ESP32 either.
This video is about one of the ESP32's radio functions, Bluetooth.
Espressif keeps their radio stuff closed for some reason. It might be due to licensing (if they bought parts of the radio), govt regulations of some countries mandating that users can't abuse the radio, or maybe it's trade secrets they want to keep secret to keep an edge on the market.
You don't appear to know much about the ESP32 and its ecosystem. You should, if you are at all interested in electronics, microcontrollers, or "Internet of Things".
As other comments point out, lots of holes.
I think nobody should pay for that.
If you intend for people to click the link, then you might just as well delete all the prose before it.
The solution seems to be to have the video "rated" in some way. Or host it elsewhere.
A function must check its arguments. It cannot assume that the arguments are already checked (against its own requirements). This is regardless of what called it, or where the values came from.
I don't see ads, thanks to ad blocking tech in browsers and smartphones. Any time that happens to fail and I get to endure an ad, I am amazed that regular people without ad blocking tech can endure this onslaught.
The time to negotiate a "middle ground" is long past. Let's not even entertain that idea.
An acceptable middle ground could have been designated areas for ads, which you have to seek out to see them. Think of the Yellow Pages.
Ad companies need to be reined in. They cannot control themselves. They are lobbying against all limits and controls. The only solution is to eradicate ads entirely and to make sure that anyone who gets that idea will never get it again.
that gave me a chuckle
You mean "not statically typed". Which also applies to Javascript, PHP, Python, ... so if that critique doesn't stick to those, it's not a critique you can level at Ruby.
"Agile/XP" is a big bag of many ideas. Some of them aren't related, but they all get stuffed in that bag.
Personally, I enjoy pair programming, which is the literal experience of dealing with an (agentic) AI for the purpose of programming.
Tests (regression tests, unit tests, integration tests, ...) make development easier in that they tell you right away when you took a wrong step. You don't have to test manually anymore, so that saves you time and concentration, and you can test a lot more often.
Those are the good bits of "Agile/XP".
"ASCII Smuggling" has been known for months at least, in relation to AI. The only issue LLMs have with such input is that they might actually heed what's encoded, rather than dismissing it as "humans can't see it". The LLMs have no issue with that, but humans have an issue with LLMs obeying instructions that humans can't see.
Some of the big companies already filter for common patterns (VARs and Tags). Any LLM, given the "obfuscated" input, trivially sees the patterns. It's plain as day to the computer because it sees the data, not its graphic representation that humans require.
- That "weather website" has to serve all of Australia.
- It's got to be usable on big screen desktops, tablets, smartphones.
- It has to have an uptime of what I estimate to be 99.99%. As the article says, farmers will pitchfork you if you can't tell them when rain will hit their fields.
- It has to be slinging dynamic image data to (about) every visitor.
- The data comes from somewhere. You're lucky if they have that under control already. Probably not.
I came up with these aspects, not knowing anything about what the "Bureau of Meteorology" actually needs in a website. It's just common sense speculation.
These places cannot and will not change. If you can, find employment elsewhere.
Any "unknown" state of the scene is bound to confuse it.
They are axing the "pull" path of the actual service. That path only supported POP for pulling those mails. There never was an IMAP pull path.
They are telling you to read your mails of the "other" account by configuring your Gmail app to access it via IMAP. That obviously won't import those mails from the other account into your Gmail account.
The solution is to push. Configure whatever system handles the "other" mail address to forward the mails to your Gmail account.
The announcement clearly says that "Check mail from other accounts" will disappear. They say it's about POP, but if the entire feature disappears, then it's not just about POP.