"Anyway, we know you might have your doubts about a virtual concert in a real-life venue"
As I read that, my Youtube feed on the other monitor is suggesting I watch a clip about Neuro-sama's concert in LA. Weird coincidence!
Though I suppose having an AI VTuber doing the concert puts the real world even closer to the corpo visionary's dream than the story is🤔
many people referred to it as the single word "Marm."
Because you either love it or hate it?
(For non-British readers confused by the joke, "Love it or hate it" is a slogan used to market the spread Marmite.)
"Well, in the end, you're just messing with databases, right? Isn't it normal to be able to manipulate the company's data freely?"
Sometimes and no. If everything you need is already in a database somewhere, that definitely makes life easier. But database or no, there are generally constraints on how you're allowed to manipulate company data. Some operational, some legal. If you could just do whatever you wanted with it, things would be a lot easier.
Why do you think things like transmission failures and ATM errors happen? It's because systems are complicated!
...If you're getting transmission failures in your internal systems, something's gone very, very wrong... And I, for the life of me, cannot work out how ATMs got involved in this conversation.
The representative method here was called "agile." ... The advantage here was speed, while the drawback was that it required advanced coding skills.
No, plenty of juniors work just fine in agile scrums. And whether Agile is faster than something more formal (like Waterfall) is very... circumstantial? It depends on the work you're trying to achieve, and how specific the deliverables are.
That 'relatively low time loss from mistakes or changes' isn't really related to the agile practice itself, incidentally. It's a side effect of developing small features. Basically, if something is wrong with the feature you're working on, you only have to go back as far as the start of the feature. But that's true regardless of how you developed that feature; A 2-week waterfall project that gets changed at the end sets you back 2 weeks, exactly the same as a 2-week agile sprint would. Likewise, a 6-month project can set you back 6 months, whether you did it as one waterfall or 12 consecutive sprints.
The key was to increase the number of iterations to maximize quality.
Iteration count isn't actually a measure of quality. If anything, it's a measure of indecision.
Neither Megumin nor I were network experts,
Yeah, I got that from your hilariously inefficient setup for The Event in book 1.
But you know, the company you're working with probably has someone on-hand or on-call who knows about networks. Most big companies have someone they can call for such things.
I'd perfectly address an external error only for the system to break down from the inside because of the technical debt accrued by my colleagues.
...Did you develop it by yourself or did you have help? You keep flip-flopping on that one.
Also, it's fairly rare for technical debt to break a system by itself. It usually just makes further development harder.
