Blackthorn

@Blackthorn@programming.dev

• Tried Kennedy Approach for C64...
  Submitted ⁨⁨3⁩ ⁨months⁩ ago⁩ to ⁨retrogaming@lemmy.world⁩ | ⁨0⁩ ⁨comments⁩
• ⁨Comment⁩ on ⁨Merge then review⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Code review can’t fix incompence though. I lost count of how many times my boss told me “review that PR well because X is not very good”. Also my point is that they are overrated, not that they are useless.

• ⁨Comment⁩ on ⁨Merge then review⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Probably unpopular opinion, but peer reviews are overrated. If coders are good AND know the project, the only thing you can do in a PR is nitpicking. They are more useful for open source collaborators because you want to double-check their code fits with the current architecture. But people here are reacting as if peer reviews could actually spot bugs that tests can’t catch. That happens rarely unless the contributor is junion/not good.

• ⁨Comment⁩ on ⁨Merge then review⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I would fire you for incompetence and sabotage. Problem solved.

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Lol I feel so old reading these replies… I learnt copying BASIC games from magazines and typing them manually on the computer.

  But jokes apart, when it comes to learning, I think the best thing is to tinker with weather language you choose and don’t worry about making the “right choices” since the start. Forget about writing “pythonic” code and don’t worry about being “idiomatic”: just build something. Building good software is not just constructs, but also knowning which subsystem to improve and when. That’s what makes experience.

  When it comes to improving, you can dig deep into the language.

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Yeah, this is also useful when learning a new programming language, even when you are an experienced coder, already.

• ⁨Comment⁩ on ⁨Which software do you mostly use for programming, and why?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Ofc I knew! Yeah, (neo)vim takes time to adjust. Personally I only use a bunch of commands, never bothered with the advanced stuff.

• ⁨Comment⁩ on ⁨Which software do you mostly use for programming, and why?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Personally, I mostly use neovim, both at home and at work. My reasons are:

  1. I hate any kind of screen cluttering. The minimap comes straight from hell.
  2. it’s very responsive. I don’t even bother using language servers as they occasionally introduce micro delays that I hate.
  3. it helps me in organizing the code better. No minimap means I keep the file size manageable, not seeing the definition of the function straight away means I keep the static complexity of the code in check (tend to reduce the number of delegates). It doesn’t help when I have to read cose from legacy codebase, but I don’t care too much about that.
• ⁨Comment⁩ on ⁨is Rust really that powerful / intuitive?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  “intuitive” is extremely subjective, and based on your past experiences. I’ve coded in C++ for years, and some Python, too and was able to grasp many Rust concepts very quickly, while for others I struggled (and still am). I’d say that if you are looking for “intuitive”, Rust ain’t it. It’s a system language, so it requires planning, it’s definitely not the ideal language to slap a prototype quickly together, expecially as a beginner.

• ⁨Comment⁩ on ⁨i are programmer⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I salute the author of this for drawing a CRT monitor.

• ⁨Comment⁩ on ⁨is it just me or GitHub is turning into some sort of LinkedIn⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I wouldn’t say it’s a new LinkedIn, but it’s definitely a defacto monopolio. It pains be that Cargo (the official rust packaging system) is so integrated with it. My own personal hobby projects are self-hosted on a gittea instance right now, but I still have a github account to contribute to a friend of mine’s project which is, sadly, hosted there.