• 5 Posts
  • 76 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle



  • I work in a company with other people. it’s not a good idea to have an idea where you have to specialise in a range of things to be successful. I specialise in programming.

    also, those benchmarks translate to better user experience which means they actually use our product, and lower hosting costs.

    frameworks and patterns reduce bugs and let us create features quickly. it’s important, if you think it’s pointless maybe it’s not for you. if you want to go do a startup instead, good luck.








  • I just made a github action that merges anything updated in master into feature branches automatically. you get pinged if there’s a conflict but the automerge keeps drift to a minimum so it’s less common and fixed sooner.

    better than merging poorly tested/reviewed code.

    and yeah, a small team of superstars doesn’t need reviews so much, but most teams have a range of devs with different levels of experience and time working with particular parts of a large codebase. Someone more senior or more expert derisks people picking up tickets and improves code quality.

    it also leads to plenty of good conversations about the best way to implement, so overall it’s a win.







  • yeah the issue honestly is how much someone else has to read to understand your code. it’s weird because the whole article is about making readable code for the next person and he never stops to address the fact that leaving 10x as much code to read might also make life more difficult.

    I feel like he just wanted to make a point about how it’s nice to make types immutable and suggest other techniques can be worth implementing too, which I agree with, but honestly his premise is a trainwreck.