...only because MS Devs are not really messing with it anymore.

You are right about the common sense part - it is exactly that. The only problem is that common sense is not common, and often the product owner may not have it to begin with. But the product owner can be sold on a methodology that gives results - and put their faith into something that is a hot keyword of cutting edge development methodology. So we sell them on this, and turn around and implement so our developers can get at least 2 weeks of concentrated time to focus on completing features and aren't ripped back and forth on a semi-daily basis from one hot feature to another. And we actually get time to develop to the feature and (more importantly) test against the acceptance criteria. And if it isn't perfect, we can refine the requirements and make another sprint. This happened in small, managed waterfall teams from the beginning of software development, but often got lost in bureaucratic mess once companies got big enough. By formalizing this small team common sense methodology, we can keep corporate interference to a minimum. They don't join scrum meeting unless expressly invited.

I remember back in middle school in the 80s working with HyperCard to set up custom stacks on the school's Macs (goofy things like choose your own adventure games, etc.). And they called them Hyperlinks back then too.

Or have a dialog that comes up and says "I can see that you have {done these steps in this order} for {this situation}. Would you like for me to make that the default activity for {this situation}?" Give the user some interaction to take the repetitiveness way. A tool works best when it lets the user choose when to take shortcuts.

I have portions of code that I reuse all the time in other projects (including freelance commercial work), and I am ethically not obligated to sign over this code because I package it as a library on GitHub with an MIT license (which anyone can then also use, too), and then use it in my other work from that source. If the client has any issues with this, all they need to do is review the code and they will see that it is sourced appropriately, and the MIT license is open enough that it won't interfere with any other license they want to slap on it.

Sounds like the Brits had some boys moonlighting for NASA down in Florida at Kennedy Space Center, which just happens to have both spacecraft and alligators...

ImpQueue Could be for ImprovedQueue...but also since imps are little demons... But, also IdxQueue could work too.

I didn't think paper could bend that way!

Tried to get my prettier half to watch the first season. She dislikes having to use her higher brain functions to understand what is supposed to be simple escapism. Halfway into the first episode, she noped herself into the next room and found something else to do. Sigh.

Varied skill levels of team members make style enforcement an important tool to be sure you can assign the work to almost anyone on your team without too much hassle about "style-stink". You just have to get buy-in from the team because enforcing it without their buy-in only increases resentment. That, and making in-line comments for hard-to-follow code blocks can make a world of difference for the guys who have to come in after you to maintain the code. That's my story and I'm sticking to it.

My wife joined my life about 11 years ago with two cats and a dog. We've since added another dog, lost the first, and added 1 cat and two horses (both OTTB ex-race horses aged 6 and 7 who will live up to their 30s most likely). All rescues. No kids, mind you, as I had that earlier with my daughter who is now off in college. Of the two cats that my wife brought into my life, they were a mother and son. The son was so attached to my wife that there was no chance I would fit in edgewise. But the mother and I found a good spot together. She's 22 now, and outlived her son (who passed away earlier this year at 20). I affectionately refer to her as the zombie cat because we can't exactly define the supernatural power that keeps her hanging on, but she knows where the food, water and litter box are located, and gets plenty of affection. She sleeps 23 out of 24 hours a day, is mostly deaf and certainly senile, and I have to admit that my reaching down to pet her each morning is mostly making sure she has made it through the night. But wife and I have both agreed that as long as she still does everything and responds to affection with a purr, then we will refrain from taking her to see the vet. There is nothing like the love I have for my kid, but the love I have for any of the animals that have wriggled their way into my life is a very close second. I completely understand what you are up against...we welcome them into our lives, knowing full well that we will outlive them and end up saying goodbye much too soon. But don't let that stop you! If you have the room in your heart and home, go down to your local shelter and make a new friend.

Took this a step further and extended the code, and it should work with culture:

void Main()
{
StringBuilder builder = new StringBuilder();

Enumerable.Range(1, 12)
    .ToList()
    .ForEach(e => PopulateDayOfMonth(2021, e, builder));
    
Console.WriteLine(builder.ToString().Trim());

}

static void PopulateDayOfMonth(int year, int month, StringBuilder builder)
{
builder.AppendLine();
int space = 6;
int dashLine = 1 + (space * 7);

IEnumerable days = Enumerable.Range(1, DateTime.DaysInMonth(year, month))
    .Select(d => new DateTime(year, month, d));

builder.AppendLine(days.First().ToString("MMMMM"));
builder.Append('-', dashLine);
builder.AppendLine();
builder.AppendLine($"|{string.Join("|", Enum.GetNames(typeof(DayOfWeek)).Select(d => $" {d.Substring(0, 3)} "))}|" );
builder.Append('-', dashLine);
builder.AppendLine();
DayOfWeek dow = days.First().DayOfWeek;

while (dow != 0)
{
    builder.Append(' ', space);
    dow--;
}

bool first = true;

foreach (var d in days)
{
    if (!first && d.DayOfWeek == 0)
    {
        builder.AppendLine("|");
        builder.Append('-', dashLine);
        builder.AppendLine();
    }

    builder.Append($"|{d.Day.ToString().PadLeft(space - 2)} ");
    first = false;
}

builder.AppendLine("|");
builder.Append('-', dashLine);
builder.AppendLine();

}

With the following output:

January

| Sun | Mon | Tue | Wed | Thu | Fri | Sat |

                          |   1 |   2 |

---

| 3 | 4 | 5 | 6 | 7 | 8 | 9 |

| 10 | 11 | 12 | 13 | 14 | 15 | 16 |

| 17 | 18 | 19 | 20 | 21 | 22 | 23 |

| 24 | 25 | 26 | 27 | 28 | 29 | 30 |

| 31 |

February

| Sun | Mon | Tue | Wed | Thu | Fri | Sat |

  |   1 |   2 |   3 |   4 |   5 |   6 |

---

| 7 | 8 | 9 | 10 | 11 | 12 | 13 |

UX (User Experience) and UI (User Interface) really are two sides of the same coin. UI design is all about design that fits the function of the program. UX is how the user feels about the interaction with the interface. You can have a great design, for instance, but the user experience will fall flat due to issues with performance or in the consistency of the interface. A good example is with operating systems and file browse/open/save dialogs. If an OS uses a cohesive strategy, then application developers use the same toolbox to access dialog interfaces, which makes the user experience (at the very least) predictable from one application to another. Without this consistency, every application has its own dialogs, which makes the experience from one application to another jarring. Also, user experience is about knowing your target audience, and then fine tuning the interface for that audience. For instance, if most of your audience is hard-core programmers, they won't be scared off by CLI commands to perform everyday functions. But if your target audience isn't technically oriented, presenting them with a CLI will only push them to the next product in line.

My style too. Sometimes it gets a bit too indented, but it is far preferable to side-scrolling to make sense of what you are doing with LINQ extensions and Lambda expressions.

Considering I left the house this morning without power, I suspect this to be the case right now since my neighbor kindly informed me that the power was back on. Good news is the fridge/freezer was already empty in advance of my vacation later this week.

You know, even if it is under warranty, and the memory is user-accessible, I would try removing and resetting the memory just to be sure it isn't just a loose stick of memory. Would suck to send it all the way back to the service center just to have them diagnose a loose memory stick. On another thought, it could also be chaffed/loose wiring/harness. There are a lot of devices located around the screen (besides the screen itself), such as cameras, microphones, indicator lights and multitouch sensors. If you happen to have the lid open anyhow, look for areas where the wire insulation may have worn through by rubbing together or on something. Some electrical tape and/or heat shrink tubing may be all that's needed to solve the issue, saving you from having to buy a new laptop.

Yeah, MariaDB was forked from MySql by former MySql developers just after the acquisition by Oracle. It has drifted from MySql a bit during the years of development since, so if you are developing to Oracle MySql, you would have to do some reconfiguration for it to work properly with MariaDB.

Possibly...go to ASP.NET Core so you can run on a POSIX host? If you need a non-MS database, take a look at PostgreSql. It has hooks into both Dapper and EntityFramework Core if you're using an ORM without a terrible amount of hassle.

As long as all the other cars on the road were also self driving... Otherwise, nope. I trust the software to do the right thing. I don't trust other (unpredictable) human drivers.

It's a valid worry whenever Microsoft is involved. Just because the lion has laid down with the lamb doesn't mean lamb isn't on the menu anymore. It just means that it's convenient at this time. Who knows what tomorrow will bring?