karlhungus

@karlhungus@lemmy.ca

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨10⁩ ⁨months⁩ ago⁩:

  Interviews are a crapshoot, and feedback from them is usually valueless. Good luck to you in your future interviews

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

  I hear this quite a bit, and think there’s actually a good deal of nuance to it. I’ve seen places that insisted on comments for everything, and it was silly, a significant number of comments had no value. This made people not read comments, as opposed to other places I’ve worked with very few comments - when you ran across a comment you gave it more weight (something here was complex, or not as simple as it seemed).

  So imo, use comments which can communicate effectively, but use them sparingly for important parts that are complicated, for the rest attempt to communicate with the code itself.

• ⁨Comment⁩ on ⁨Systems engineering in the software industry⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Probably my quotes implied sarcasm, what i should have said is there are so many hats that a “software developer” or “software engineer” is really really broad like by the wikipedia definition at my current company we typically call those “principal engineers”, or “principal architect”; i’ve also seen them called staff software engineers.

  Likely it’s super domain dependent; the failure cost with a satellite’s or hardware cost you the business. Where with a website the MTTR can be very small. So a large oversight isn’t quite as needed, as the cost is so small.

• ⁨Comment⁩ on ⁨Systems engineering in the software industry⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  If you described what a “systems engineer” did that’d be a big help.

• ⁨Comment⁩ on ⁨NodeJS vs Go⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Personally i prefer go, but these are pretty standard languages; so learning the in’s and out’s really isn’t all that time consuming (you aren’t going to have to change how you think about programming like say rego). Since you have python experience these should be no big deal, but maybe worth playing with a bit if you are trying to get a job in either language and need to cross off that bullet.

  As for expanding your learning, i’d try something like functional programming (haskell), or query language like rego above. Neither of these will be great for your resume though.

• ⁨Comment⁩ on ⁨How do you shell expand your variables and why?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I do what the linter tells me to: github.com/koalaman/shellcheck

• ⁨Comment⁩ on ⁨What's your favorite CICD tool?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  We use build kite, I like it better as an end user than other things I’ve used (circle ci, Travis, bamboo). I haven’t been on devops setup end of it much so can’t really talk to that end. I’ve liked what I’ve used of gh actions as well.