Just a basic programmer living in California

  • 0 Posts
  • 54 Comments
Joined 2 years ago
cake
Cake day: February 23rd, 2024

help-circle


  • The first season, and the first few episodes of season two take some extra weird turns because of the revolving door of producers during that period. The original producer left the show during season one. Then a duo took over who took the story in quite a different direction. Those two left in early season two. After that production finally settled into a more stable state.

    Anyway the characters and acting are great, and that counts for a lot!


  • They set a high bar with the first two seasons.

    I felt like there were highlights in season 3. But it also felt uneven. The episodes I liked felt good, but not great. The first two seasons had great episodes.

    There was also a distinct lack of social commentary, which I feel is important in Star Trek. The best we got was Terrarium. Definitely a fun episode, but it’s core is a trope we’ve seen a number of times. What Is Starfleet looked like it was thinking about commenting on something, but frantically pulled the ripcord partway through, and went in a direction I wasn’t comfortable with. (Which is too bad because I thought the directing in that episode was very cool.) There’s nothing on the level of Ad Astra Per Aspera. Instead we got 5 episodes of mortal struggle vs unreasoning monsters.

    the list of unreasoning monsters

    Gorn, plant zombies, the “pure evil” on Vadia IX, the ship-eating ship










  • My work is using Coderabbit, and I’ve found its feedback to be pretty helpful - especially since I’m working with a language I don’t have a whole lot of experience with (Python). I check what it tells me, but it has taught me some new things. I still want human reviews as well, but the AI can pick up on detail that is easy to skim over.

    It doesn’t cover bigger picture stuff like maintainability, architecture, test coverage. Recently I reviewed a PR that was likely AI generated; I saw a number of cases where logic duplication invited future bugs. (Stuff like duplicating access predicates across CRUD handlers for the same resource, repeating the same validation logic in multiple places.) Also magic strings instead of enums, tests of dubious value. Coderabbit did not comment on those issues.

    I’m also getting feedback from Sonarqube on the same project, which I think is static analysis. It’s much less helpful. It has less to say, and a lot of that is pointing out security issues in test code.


  • I did the swipe to complete an -ing suffix, and yes, I see the appeal!

    Entering punctuation is a bit slow using long-presses on the apostrophe key. Maybe I can get used to using the symbol layer instead.

    Oh! You can swipe from the 123 key to type a symbol from the symbol layer in one gesture! That’s great! It even works for comma! Kinda accidentally - given the comma position I’m swiping over question mark, backspace, comma which gets a net result of typing just the comma. I wish it would go back immediately to the ABC layer.

    Moving the cursor by holding and dragging from space feels better than the similar feature in gboard!

    I miss the gboard backspace feature where you can hold and drag to selectively delete.



  • Strange New Worlds is great! Since you’ve already seen DS9 and TNG that’d be my next pick for most enjoyment.

    Discovery and Lower Decks are good too! But Picard doesn’t get my recommendation.

    Watch order isn’t important. There’s a little crossover between Discovery and Strange New Worlds, but you there are only two details from Disco that carry into SNW, and those are recapped thoroughly in SNW.

    There is a little interaction between SNW and Lower Decks

    SNW / Lower Decks

    There’s a great crossover episode in SNW season 2. It’s worth getting to know the Lower Decks characters first to get the most out of that episode.

    There are three TOS episodes that are especially relevant to SNW from what I recall. The one I recommend watching is Balance of Terror.

    SNW / TOS

    SNW has lots of references to Pike’s “fate”, which you see in the TOS episode Glass Menagerie. It’s optional IMO. Btw Glass Menagerie includes a recut / retelling of the unaired pilot, which is my favorite episode of TOS. But the pilot doesn’t have the beep chair.

    Season 1 has an homage to the TOS episode Balance of Terror. It will make more sense if you’ve seen that episode. And it’s one of the best TOS episodes.

    Season 3 has an appearance from a character who first appeared in the TOS episode The Squire of Gothos. It might add some context. Also optional IMO.


  • Fugitive, the vim / neovim plugin. It does everything the CLI does, but uses vim interfaces very effectively to enhance the experience. For example it’s quite good for selectively staging changes from a file. I also like the option to open a buffer with the version of a file from any specified commit.

    I also tried neogit which aims to port magit to neovim. I didn’t like it as much. Partly because as far as I could tell at the time it lacked features compared to fugitive. But also because it seemed to want me to do everything through UIs in its own custom windows. Fugitive is integrated more thoroughly into vim via command mode, and special buffers.


  • I usually use git add -p to selectively stage hunks. But in git add -i I think running the patch command does the same thing to get into patch mode.

    If patch mode shows you a hunk, and you only want some of the lines you can press s to split into smaller hunks. Then you’ll be prompted whether to add each smaller hunk separately.

    If you want to stage a change that is on the same line as a change you don’t want to stage, or on an adjacent line, then you need to use e to edit the hunk. Git stages whatever changes are left when you’re done editing. The file in the working tree on disk is unchanged.



  • It’s hard to predict the future, but I can point to a couple of indexes.

    TIOBE measures language popularity according to a variety of factors. It has Java on a steady downward trend over the last couple of decades, but shows it as still very relevant. TIOBE does not show comparable growth for Golang. I don’t see much growth in the top 10 for languages that are especially suited to autoscaling. C# looks to be steady as a language in a similar niche as Java.

    OTOH another survey from devjobsscanner that looks purely at job postings shows Java openings as very steady over the last couple of years. It also shows Java as more popular than Golang.

    So I don’t know exactly what conclusion to draw from that. But learning a new language can be a helpful exercise regardless to broaden your perspective, and to keep your skills sharp.

    Personally for the purpose of producing resource-efficient binaries for scaling I prefer Rust. It’s design incorporates some correct-by-construction strategies that promote high-quality code. And it’s well-suited for compiling to WASM so you can do stuff like deploy small services to Cloudflare workers for wild scaling. But I guess Rust isn’t making a big showing in the popularity charts. And Golang is popular for its lower learning curve.