Many fall in the face of chaos, but not this one, not today

  • 4 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle






  • TBF all the jobs are a decade old and written by our researchers in dotnet framework as Winforms apps I hacked up to be console apps so it’s gotta be windows. I’m converting them one by one to dotnet core and moving them to my Linux containers but it’s a slow process and I’ve got a v1 release to prepare for next month.

    Everyone is just stoked that no longer do a half dozen researchers have to twice a day log in to their pet server, open their Winforms app, run it, and copy paste the results to a shared drive. Now my docker harness does it all on a scheduled task triggered automatically from rundeck server I manage. WE’RE LIVING IN THE FUTURE BABY






  • This is why I love more abstract systems like Fate Core or Cortex Prime. They’ve got systems flexible enough to be turned into really anything you want. I ran a Fate Core game for a year that had tons of cooking and feasts, modeled off of the Redwall books. The heros were always preparing some feast or finding some new food to forage.




  • I suppose this is a hot take, but I’d never intentionally select a closed source paid database or programming language. Your data is the most valuable thing you have. The idea that you’d lock yourself into a contract with a third party is extremely risky.

    For example, I’ve never seen a product on Oracle that didn’t want to migrate off, but every one has tightly coupled everything Oracle so it’s nearly impossible. Why start with Oracle in the first place? Just stay away from paid databases, they are always the wrong decision. It’s a tax on people who think they need something special, when at most they just need to hire experts in an open source database. It’ll be much much cheaper to just hire talent.

    Meanwhile I’ve done two major database shifts in my career, and you are correct, keeping to ANSI standard SQL is extremely important. If you’re on a project that isn’t disciplined about that, chances are they are undisciplined about so many other things the whole project is a mess that’ll be gone in ten years anyway. I know so few projects that have survived more than fifteen years without calls for a “rewrite”. Those few projects have been extremely disciplined about 50% of all effort is tech debt repayment, open source everything, and continuous modernization.


  • I don’t think it’s going away until ECMA supports native types. Until then it’s the best game in town.

    If a team decides to move away from it, it’s only few hours work to entirely remove. So even if it’s going away, it’s risk free until then.

    But I cannot imagine why any team would elect to remove Typescript without moving to something else similar. Unless it’s just a personal preference by the developers who aren’t willing to learn it. It removes so many issues and bugs. It makes refactoring possible again. I think teams that want to remove all types are nostalgic, like a woodworker who wants to use hand tools instead of power tools. It’s perfectly fine, and for some jobs it’s better. But it’s not the most efficient use of a team to build a house.