iOS Swift developer with an unhealthy amount of Android and Flutter thrown in. Cycling enthusiast. Admirer of TTRPGs, sometimes a player, often times a GM.

  • 0 Posts
  • 25 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle






  • I enjoyed it. The only thing I would say is that there wasn’t a lot of tension or risk of loss in the series. It was more a low key telling of a period in someone’s fictional life. It kind of left me wondering if the last episode coincides with the last chapters of the book or if the season only covers part of the book like what was done with Silo.


  • Agreed on the M1. Anything entry level for Apple is decent but not really meant to push the envelope very far. I had a 16GB Mac mini and it served me very well for software development. I had to run multiple ram hogging tools at the same time so it did have pauses when switching between them. Other than that it was a beast. It held up well compared to my higher end MacBook Pro i9 with 32 GB Ram. The M1s run very cool. You’ll wonder if your machine even has a fan except if you’re doing a long intensive processing job. The M2s from my experience run hotter. I have an M2 iPad that I’m betting becomes thermally throttled just by watching Netflix. Not that it stutters, it just becomes warm to the touch.




  • The recruiter won’t care much about why you want to leave a job. Their primary focus is to get you into a new job in order to collect a fee from the employer. The recruiter will ask you some basic screener questions while very likely not understanding what it is they are asking. If this is an internal recruiter the questions likely came from the hiring manager. If it is a staffing agency, you’re lucky if the recruiter even has a direct relationship with the company. More likely they’re one of a dozen+ companies trying to find a warm body for to put in front of the company. I often receive several LinkedIn messages for the same job in my local area from various staffing firms.

    One thing you should do is take a look at your list of negatives and turn them into positives that you have to offer a new employer. For instance, the item about many senior engineers joining and leaving can be turned into, “I have been exposed to a broad range of coding styles and architectures from working with many codebases built by knowledgable developers. Supporting and maintaining them in a production environment has allowed me to see what works well, what doesn’t, and to better my own style.” Be prepared to give one or two examples of how you were influenced by the good and the bad. If I were interviewing you, I would ask for them.

    Regarding your first two bullet points, you probably shouldn’t be interviewing for junior positions with four years of experience. Make sure that you’re interviewing for mid-level positions. It’s rare to be asked why you want to leave your current position. If it happens just say that your company is in a hiring freeze and that you’re doing the work of a mid level programmer but are unable to be promoted and that you need the extra income to purchase a house.


  • I used to work for a ttrpg company. A dice parser is not a small undertaking. You’re basically writing a calculator with an embedded random number generator. It’s fun but not an easy first project. My advice would be to keep it simple to start with and have your command interface (repl) just accept simple roll commands like roll dex and that handler knows how to make a dex roll. Simple roll commands like roll d6 are also easy to parse out with just a regex. Honestly, I think you would be better off writing a gui app and give it a retro hacker look than going with some type of terminal. Typing on phones is a pain vs tapping buttons.


  • Breaking change. It’s gone from plain text to a markdown formatted text (possibly). There’s changing an interface (obviously a breaking change) and then there’s changing the semantics of a function. I just dealt with a breaking change where a string error value changed for an account registration api call. Previously it returned EMAIL_IN_USE and now it returns EMAIL_TAKEN. Same data type but it broke the client code. Changing values or formats is a breaking change. In your case the documentation says don’t rely on this function for anything but once the output is in the wild any monkey can start using it for anything and it can’t be certain that some code documentation will be consulted before deciding to depend on it.






  • If you’re following agile it is important for a team to agree on a definition of done for a story. If you don’t have one ask the scrum master to start that conversation or bring it up in a retro. One of the things that everyone can usually agree on is that the tests pass. Throw in a minimal coverage threshold as well. It’s not an indicator of good tests but it will tell you when there isn’t enough.

    You mentioned that you’re doing this work for a client and that they will take over the code. Verify with management (in your company) if there are any quality measures specified in the contract. You don’t want your guy not performing up to the client’s expectations and you having to put in a lot of last minute nights and weekends to get there.



  • Story wise they didn’t leave much room for a sequel. It gets wrapped up nicely at the end. I didn’t play any of the DLC but the impression that I got was that a lot of possible sequel material was covered in them. The game was really good and definitely worth picking up on a sale price. It will give BotW vibes but don’t think of it as a clone. It’s got a good story and a nice little twist at the end. The boss fights were a joy if not painful at times. The puzzles were mostly good and not too obtuse. I think I had to use Google on a few of them. It is annoying with the extra clothing and style purchases that the game tries to get you to spend real money for. It tarnished an otherwise good game.