• 1 Post
  • 26 Comments
Joined 1 year ago
cake
Cake day: July 13th, 2023

help-circle



  • Cars have always been a subscription model, albeit in quotes.

    You want to drive somewhere? You’ll need fuel.

    Have driven a certain amount of miles? You’ll need to service your car.

    Driven even more? Replace tires.

    Brakes.

    Fossil cars was a money printing machine.

    That’s why the margin on sales are so low, the dealerships and manufacturers make it up over the lifetime of the car.

    Electric cars threatens that model and we see manufacturers scrambling for more ways to make money so they have a leg to stand on when service costs drop.

    In the meantime Audi e-tron owners seems to have little issue paying $5-600 for an “inspection” and another $4-500 (in total) for service items, including replacing a “leakage canister” (IIRC).

    And best of all. When your car is old enough you come back for more.

    It’s not like car manufacturers can twist our arm and make us go all in on subscriptions.

    It’s happening because people are ok with putting their money down that way.

    If we weren’t it would all be a failed experiment and everything would go back to normal.

    The funny thing is how some manufacturers actually offer value added services as a subscription, while others - looking at you BMW and Toyota - are trying to de-content the car to put things on subscription instead.

    I’m fine with value added services, less so with seat-heaters as a service.

    That’s the kind of thing that - down the line - ends up with “oh sorry, we turned the server off so you can’t ever have heated seats again”, or in the meantime “server was down so heated seats didn’t work for two weeks in the middle of winter”.








  • Step one: Create random package that does something trivial that’s done often.

    Step two: Start making PR’s to lots of open source projects replacing a number of lines of code with your new package.

    Step three: Work hard to get your package into another package that’s used by many.

    Step four: Update your CV to reflect that you build software that thousands of companies depend upon.

    Step five: Profit from the stupid incentives created by companies hiring people that pad their CV’s by making redundant software and push them into everything they can to make sure everyday is dependency hell.


  • Sounds like an esoteric thing to do.

    To begin with; Teams isn’t a very friendly thing to run in the first place.

    Then you want to run a virtualized windows instance, multiple maybe even, so that you can run Teams in these instances?

    Would that be x64 windows? Virtualized, running on Rosetta, on an ARM CPU?

    I guess if your only goal is to find out, sure.

    But if you want to virtualize windows, why start with a mac?

    I know someone who took a CPU out of the socket with the system “running” and then put it back in and resumed operations.

    Sure, it can be done. But everyone else will just unplug the power and be done with it.

    In the meantime I can wholeheartedly recommend Apple Silicon, but Microsoft’s software is still the worst stuff that I run on my mac.

    Also, you can just use Teams from the browser if you don’t need any integrated features.




  • I’m always wary when someone talks loudly about architecture.

    I’m not saying it’s not important, by all means, but in my 10 years as a professional developer I’ve found that the people who are most devoted to preaching architecture don’t contribute to good architecture.

    I’ve only met a few persons that fit that bill, so obviously nothing statistical, but the experience has left me wary when people start to become loud about it.

    I’m not saying this is you, but if everyone is pushing back it might just be that you are part of the problem, not the solution.

    Architecture can be many things.

    However, there are individuals who believe that the only way is that one way they read about in a book once, or even worse, they’ve read it multiple times and it’s their Bible. Maybe they’ve read multiple books by the same author and has basically adopted someone else’s viewpoints without any critical thinking.

    Exposing yourself to different architectural strategies, viewpoints on architecture from multiple people.

    And remember that all architecture serves a point. It is the job of the architect, and the team, to build an architecture that solves the needs of the project.

    “Clean code”, whatever that is interpreted as, is probably not one of them.

    “Good test-ability”, modularity, multi-platform, performance, package-size, internationalization, accessibility, etc. might on the other hand be needs and goals that can be used to guide the project architecture.

    Uncle Bob’s layer cake probably isn’t.

    If you want better takes than mine on criticisms of Uncle Bob’s Clean Code I suggest to Google it. It might cause you to re-think some things as well.


  • Definitely seems to be trending that way.

    But honestly that’s been my experience on all Internet forums I’ve been a part of.

    In the beginning they’re places with few, but good, discussions, but over time as their gravity exponentially attracts more people the level of quality drops until you have people who get angry at you because they’re on the wrong side of the Dunning-Kruger effect.

    I always strive to learn new things, and I hope that when I’m completely off the reservation about something and someone tells me I have the good sense to take a step back, learn something new, correct myself, and hopefully improve until next time.


  • The Internet is full of people to argue with, if that is what you’re looking for.

    I once tweeted at a guy who had gotten his name on an editorial about how Apple Pay (and Google Wallet/Pay) would fail as Walmart (IIRC) now had launched their own app-based payment service.

    My tweet was just that he completely overlooked that Apple and Google had device level integration and a wider reach, and that Walmarts wallet-thingy thus would be competing with a lesser customer experience and way fewer supported locations.

    His response was something along the lines of “boy, you really meet the crazy ones on Twitter”.

    I think the fediverse might work out, but on the other side - a bit less social media never hurt anyone.



  • Thanks.

    Again though, I think the why’s point back to the same thing.

    Salaries in tech in the US has been boosted by ridiculous high demands.

    Accountants don’t understand that skills and knowledge is something you pay for and just see that one dev in India costs 1/5 of one dev in the US.

    Heck, even I’m cheap compared to the average US devs and I live in Norway.

    But why do all these other companies do the same thing? Because they’re bandwagon companies. If FANG does something they’ll do the same.

    I also read once that recessions hit the tech industry first, but it also bounces back first.

    If that’s correct I have no idea, and I’ve yet to go through a proper recession in my career, but it’s definitely clear that we are busy making one.

    All the companies going like “we need to be inflation winners”, I know mine does.

    As for outsourcing to India, that always goes in waves. Hard to build good tech there. It’s only cheap in the beginning. Too much instability and job switching.



  • ChatGPT is, despite popular consensus, not an AI.

    It’s a system that has some notion of context and a huge database of information and is really good at guessing what words to put on screen based on the provided input.

    It can’t think of anything new or novel, but can generate “new” output based on multiple sources of data.

    As such, it will never be able to design a fusion reactor, unless it’s been trained on input from someone who actually did.

    And even then it’s likely to screw it up.