I liked it and got a 7 space 4.

Is this the max score? How can I know? It wants me to login for a reveal… which is unfortunately where I bounced. Maybe I would sign up after a fews days if I got hooked because I found it really annoying when I lost my wordle streak.

You mean the full internet experience in one window thing like the aol browser? I’m pretty sure I used to use it, light blue thing and hotmail a more seemless integration?

My grandpa has MSN as an ISP and would dial in using a fully featured, very blue windowed program that had everything Internet in it. I remember thinking it was pretty cool.

Now I feel old, lol

Mildly visible even in London. Better with camera phone but definitely just visible after you let your eyes adjust

I can imagine that if we ever reach a point where the interviewers are prepped with the useless corporate answers to these reversed interview questions, it means we’ve done a great job in pushing to get the right information and gets right to the crux of their issues and possible red flags, one of which might even be a “corporate culture cover up stock answer”. Then surely just a follow up question asking “is that also you personal experience here?” And if you still get a corporate answer then you know for certain it is a red flag. Ultimately it sounds like these sort of questions could work well.

From what I’ve read on Wikipedia, mixxx apparently uses the xwax source code. As does PiDeck. It would be really interesting to know what else uses it.

Serato DJ Pro and Traktor probably

Xwax is amazing. But what was more amazing to me was that the magic external box with Final Scratch was actually just a sound card and the rest was all software. Dunno if I am over simplifying but it was amazing to see that the time coded record and the software like xwax was all that was actually needed.

Acquiring one of these "ScratchAmp" boxes that was missing its software is what started the whole project. These earlier systems deserve a lot of credit. If I'd had access to the software I don't imagine I would have dug so deeply into the concept.

This is quite good advice, I feel the “we have to do this anyway” line is more like… “so we might as well make it easy for ourselves”… eg write code that works, you self tested it through tests and manual if needed, so the reviewer doesn’t have to get bogged down in actually running it (start by adding screenshots for this but graduate to not needing them). Keep PRs as small as possible, aka multiple PRs streaming after each other for a single feature card, get the PRs in as soon as valuable and don’t block for nitpics but the shared expectation you start to agree on things that are better and they happen with the next changes.

The general mantra being that “if it works then it shouldn’t be blocked” and developer can choose to improve the maintainability there and then or delay it to next or later PRs at their discretion. After all you trust each other.

That reminds of codebases littered with Todos… where I like to Yoda it… do or do not, there is no todo.

A TODO is not inherently bad, but I think intent is important— how likely is it that someone will come back here purely with an intention to address that comment? If not likely, then the TODO will be taken up in the context of future refactoring and in that case it's a gift to the person eventually contemplating that work, helping them understand something about the code or context that you realised too late in the project to be able to act on it.

Ah that makes sense now. I nearly said it was like excalidraw, which is really nice for architecture diagrams more than for ui/ux I find.

Perhaps more like Tekton, which was like a classier crisper comic sans