Cool, and then there’s NEVER any problems with different paths? With back and forward slashes? With the limit on path length? With missing permissions on the file system requiring weird workarounds?

Nope. The language we use handles that for us. I don’t think path length has been an issue for a while now?

Most importantly, your server is likely not Windows, yet you test on Windows, and that’s never ever been a serious source of issues?

We use serverless functions using Linux and it’s never an issue. My previous employer, we had Windows servers and Linux based containers, and that wasn’t an issue either.

I never use Powershell and I use the terminal daily.

You install git and you get git bash that works great in the Windows terminal. That’s something you do once. I use the terminal daily, not an issue at all.

Personally I’ve never experienced any performance issues with it, seems fast and responsive to me.

I dev every workday on Windows 11 and I don’t get why people feel like it’s awful to work on? I dunno what everyone else is doing but it’s basically just switching between the IDE, Slack and the browser. The OS never seems to be an issue for me. My only real gripe is that even I click update and shutdown at the end of the day, it updates and restarts.

Same for my colleagues using a Mac.

I’d be more bothered about using Teams over Slack

Do you plan on adding any + subscription features?

I think that’s the result of dependency injection.

public interface ICanTravelThroughTheAir
{

}

public class Flea : ICanTravelThroughTheAir
{

}

public class AircraftCarrier
{
  private readonly List<ICanTravelThroughTheAir> _aircraft = new();

  public void AddAircraft(ICanTravelThroughTheAir flyingThing)
  {
    _aircraft.Add(flyingThing);
  }
}

public class Dog : AircraftCarrier
{
    public void Woof()
    {
        Console.WriteLine("Bitch I'm an aircraft carrier!");
    }
}

public static class Program
{
  public int Main(string[] args)
  {
    var dog = new Dog();
    
    for (var i = 0; i < 10000; i++)
    {
        dog.AddAircraft(new Flea());
    }

    dog.Woof();
  }
}

However you’re on Debian stable and the latest version of the package that came out 24 years ago is still too new.

When you log into the console and all your shits gone and you start to have a mild panic, when you suddenly realise it’s switched you to a different region.

Why would they have to come in at 7am?

• Spending a day or more every quarter/half sorting out your roadmap, prioritising stakeholder needs, tech debt and enhancements
• Someone from senior leadership decides they want random thing they invented and blows the roadmap up
• Much wanted feature (X) or issue gets pushed back
• CEO makes a comment in a company wide meeting how they can’t understand why we simply can’t do X thing yet
• Everyone in Product scrambles to make X a priority
• Go to step 1

Yeah. The last thing I want to do when I’m not working is to get on another computer.

What is it about Java where companies are hesitate to upgrade? Do the Java releases always bring breaking changes or are the companies that use Java have a culture of not prioritising tech upgrades?

In my mind a simple unit test should have caught this. Mock out the call to the service that sends the message and verify that it’s been called with the correct message, and cover the possible failure scenarios. That said I hate loosely typed languages lol.

This isn’t the languages fault, it’s the developers.

This is depressing, Blackpool would remain unscathed.

Well yeah strictly you don’t, but the idea of having a single machine under someone’s desk as a build server managed by one person where you have multiple dev teams fills me with horror! If that one person is off and the build server is down you’re potentially dead in the water for a long time. Fine for small businesses that only have a handful of devs but problematic where you’ve multiple teams.

Bottom line for most business though: As long as the cost makes sense, why bother self-hosting anything. That’s really what it comes down to. A bonus too, as most companies like being able to blame other companies for their problems. Microsoft knows that, and profited greatly with Windows Server/Office/etc. for that very reason.

Yup, exactly this. Why waste resources internally when you can free up your own resources to do more productive work. There’s also going to be some kind of SLA on an enterprise plan where you can get compensation if there’s a service outage that lasts a long time. Can’t really do that if it’s self managed.

I’m talking about in a professional environment. You basically need a team to manage them and have a backlog of updates and fixes and requests from multiple dev teams. If you offload that to something cloud based that pretty much evaporates, apart from providing some shared workflows. And it’s just generally a better experience as a dev team, at least in my experience it has been.

It’s not like internal build servers are 100% reliable, scaleable and cheap though. Personally I’ve found cloud based build tools to be just a better experience as a dev.