« first day (4229 days earlier)      last day (83 days later) » 

00:21
REFRESH! There are 5325 unanswered questions (93.1266 answered)
 
11 hours later…
10:59
0
Q: Advent of Code 2024 - Day 1 (Common Lisp)

advent-of-code-askerI have recently started learning lisp by reading ANSI Common Lisp, and I thought advent of code would be good for practice. Any feedback on my code for Day 1 would be appreciated. (require :uiop) (defparameter *input-file* "01-input") (defparameter *input-lines* (uiop:read-file-lines *input-file...

 
1 hour later…
12:31
0
Q: Can you help me speed up this SQLite query?

marko kraljevicI have two tables: month (thread) and company (comments in thread), here is the Better-Sqlite schema: db.exec(` CREATE TABLE IF NOT EXISTS month ( name TEXT PRIMARY KEY, -- "YYYY-MM" format for uniqueness threadId TEXT UNIQUE, createdAtOriginal DATETIME, createdAt DATETIME DEFAU...

13:03
@toolic @toolic I am not going to vote to close this question. It has 3 up voted answers, one was accepted. I did edit the title.
13:52
@pacmaninbw also: it was an X/Y problem and the historical answers fully whiffed.
14:08
@Reinderien I saw your new answer, does that mean you think the question should remain open? The mind reader comment in the answer might indicate not.
I was being tongue-in-cheek. If it were posted new and had no answers, I would VTC. But since it has several half-decent answers (even if they do miss the point), I see no problem with it staying open
14:48
0
Q: Simple Sieve of Eratosthenes

VesselI've implemented this version of the Sieve of Eratosthenes in Rust, with inputs. I'm mostly pleased with it, but want to know if the input logic can be simplified, and if the sieve itself can be optimised. use std::collections::HashSet; use std::io; fn main() { println!("Enter the number to ...

 
1 hour later…
15:55
Hopefully another zombie has been put to rest.
 
1 hour later…
17:07
And hopefully one more C program Zombie slain.
@pacmaninbw Just because it was answered, doesn't mean it should remain open.
The scope changed a lot in '14.
It did receive a fresh answer though.
I'm not sure how useful it is to write answers to such old questions @Reinderien
Why are people dealing with old, answered questions lately?
Leave them alone, consider the questions from before '14 to be a different site.
A pre-cursor.
@Mast Fortunately or unfortunately I agree that we should leave questions from before '14 alone.
If they're unanswered and not in the current scope, we can close them.
There's not much else to do with them.
Considering that I joined in 2015, I may not be aware of the change in scope.
I imagine that's going to be a growing problem as time moves on, not everyone has read the metas from that period.
17:22
And my laptop battery is finally going dead for today. TTYL
@pacmaninbw There was a bit of a shake up at the end of '13.
16
Q: Winston Ewert is no longer a moderator?

JamalI've just now noticed the missing diamond on his profile, along with this: There's no announcement on Meta, and this just seems like an abrupt change. I'm not sure how long ago this was, either. But I probably should've suspected something when it seemed to take a tad longer for my recent mo...

48
Q: How is Code Review doing right now?

Grace NoteI’m Grace Note, a Community Manager at Stack Exchange. Normally for most sites we run a community site evaluation, as explained in this Meta Stack Overflow post under Public Beta sites. However, these reviews involve comparing our site content against searches on the internet for competing answer...

The first led to Jamal becoming moderator, the second spawned Call of Duty.
54
Q: Call of Duty - We're on a mission

Mathieu GuindonThis is a direct reply to Grace Note's recent CR review, more precisely the following part: (emphasis mine) Unanswered Tying in to all of the above is one of the most pressing concerns about the site I had in my own review, which is the gigantic pool of unanswered questions. There are, ...

@rolfl and 200_success were appointed.
We went through some activity changes.
In '15 the site was booming.
In '14, there were 3 canned close reasons:
8
Q: Revising list of closure reasons

200_successFollowing up on a past discussions, I'd like to tweak our list of off-topic close reasons. We may have up to three canned reasons. Currently, they are: Questions asking for code to be written to solve a specific problem are off-topic here as there is no code to review. Your question mu...

We've always had more rules about code being on-topic, but until we got the new mods (jamal, rolfl and 200_success) not a lot of that was being actually enforced.
People started caring about quality of questions.
I'd swear it wasn't just that, but I can't find the 10yo meta I'm looking for.
17:52
@pacmaninbw n1
@Mast Normally I would agree, I but I felt compelled in this case to correct the record because of the pretty severe X/Y miss that occurred.
 
2 hours later…
19:43
Monking
@pacmaninbw Thank you I realized after posting the comment I should actually... you know Google the term XD -- hence the removal of the comment.
The include mechanism in C and C++ actually imports the contents of the file into the file doing the include. If there are no include guards the file may be included multiple times.
@Peilonrayz And I removed the comment @Mast added as a reply.
@Mast It was a mess in '13 and '14. SE appointed some good mods.
@pacmaninbw Oh, I hadn't seen Mast's reply. Thanks.
 
3 hours later…
23:02
possible answer invalidation by Alexander Ivanchenko on question by Malde: codereview.stackexchange.com/posts/294584/revisions
possible answer invalidation by Alexander Ivanchenko on question by Malde: codereview.stackexchange.com/posts/294584/revisions
possible answer invalidation by Alexander Ivanchenko on question by Malde: codereview.stackexchange.com/posts/294584/revisions
possible answer invalidation by Alexander Ivanchenko on question by Malde: codereview.stackexchange.com/posts/294584/revisions
possible answer invalidation by Alexander Ivanchenko on question by Malde: codereview.stackexchange.com/posts/294584/revisions

« first day (4229 days earlier)      last day (83 days later) »