• 1 Post
  • 68 Comments
Joined 3 months ago
cake
Cake day: February 23rd, 2024

help-circle


  • A big peeve of mine is when someone says they did something, “I remodeled my floors, I painted the walls, I fixed my car, i put in a fence”, when they really mean they hired people to do these things. It’s straight up taking credit for other people’s work and it’s normalized.

    I grew up poor where hiring help was rare so when someone said they did something, they always said it proudly and they meant they did it themselves.

    Now I always ask and point out they didn’t do anything. I’m really fun that way. But honestly i think the language matters. For big jobs i personally say I had the walls painted or I got the car fixed since that implies getting someone else to do it.


  • Microservice from the start may be a lot of overhead, but it should at least be made with that scalability in mind. In practice to me, that just means simple things like make sure you can configure it via environment vars, run it out of docker compose or something because you need to be able install it on all your dev systems and your prod server. That basic setup will let you scale if/when you need to, and doesn’t add anything extra when planned from the start.

    Allocating infrastructure on a cloud service with auto scaling is the hard part imo. But making the app support the environment from the start isn’t as hard.












  • No they’re not. And the tech literate people that will see that they can disable this protection and continue as normal.

    Microsoft doesn’t always do good things, but I think this is fine. If you open firefox it’ll ask you if you want to set your default browser, and it won’t regedit for you. It will open up the proper windows menu that lets you set firefox as the default.

    Not letting malware change your settings by default is a GOOD thing. It is also a good thing that advanced users can disable the feature.

    The only bad thing about the story is the lack of transparency. Having to find out about it by breaking tools is bad. It would be better if they had a changelog for these updates that say what they do so admins can see if their tools will be affected.


  • You’re right, I’m not representing the merge correctly. I was thinking of having multiple merges because for a long running patch branch you might merge main into the patch branch several times before merging the patch branch into main.

    I’m so used to rebasing I forgot there’s tools that correctly show all the branching and merges and things.

    Idk, I just like rebase’s behavior over merge.




  • I feel the opposite, but for similar logic? Merge is the one that is cluttered up with other merges.

    With rebase you get A->B->C for the main branch, and D->E->F for the patch branch, and when submitting to main you get a nice A->B->C->D->E->F and you can find your faulty commit in the D->E->F section.

    For merge you end up with this nonsense of mixed commits and merge commits like A->D->B->B’->E->F->C->C’ where the ones with the apostrophe are merge commits. And worse, in a git lot there is no clear “D E F” so you don’t actually know if A, D or B came from the feature branch, you just know a branch was merged at commit B’. You’d have to try to demangle it by looking at authors and dates.

    The final code ought to look the same, but now if you’re debugging you can’t separate the feature patch from the main path code to see which part was at fault. I always rebase because it’s equivalent to checking out the latest changes and re-branching so I’m never behind and the patch is always a unique set of commits.