• 2 posts
  • 43 comments
Joined 3 years ago
Cake day: July 13th, 2023
  • Isn’t that what threading is? Concurrency always happens on single core. Parallelism is when separate threads are running on different cores. Either way, while the post is meant to be humorous, understanding the difference is what prevents people from picking up the topic. It’s really not difficult. Most reasons to bypass the GIL are IO bound, meaning using threading is perfectly fine. If things ran on multiple cores by default it would be a nightmare with race conditions.

  • When people complain about Windows in a work environment, I wonder really what their complaints are. I mean I don’t like windows either but at the end of the day you’re just using visual studio and maybe a terminal emulator to access your work. Your codebase is on a test server or production server.

    That said, my mind was blown when I used my first mac. Even the best windows laptop I’ve been given at work would maybe last 4 hours without charging. I can use my Mac for almost two days without charging it which makes going to the office that much easier when I can sit outside. I don’t know if Windows is just extremely inefficient with its resource management or of it’s all the bullshit spyware companies bloat every PC with but if the company absolutely won’t let you install a Linux desktop OS I’d just ask for a Mac. Plenty of staff use them at universities

  • I think the “difficult to please managers” speaks to me. I’m a top performing engineer and I had no problems leading the pack until I had a new manager forced on me who was very much a “suit” type. He views the team as numbers and everything can be solved by “throwing more bodies at it”

    Thankfully I got promoted to a new team but yes there are many causes for burnout

  • I’m not a developer but I write a lot of code for network infrastructure automation… when I started learning I was already a network engineer so I figured it would be a cakewalk. I think it takes a certain type of person (patience, persistence, tenacity, etc) to excel in a computer science field. I’d reckon a lot of young people think the jobs are all pretty sweet and cushy

  • I have been a network engineer with no degree for many years, but I did have a lot of certs. It’d be nice if there were something similar for programming. But I’ve never seen anyone care that much about the engineer title. I’ve always thought it’s someone who understands his craft/engine design in and out, but doesn’t design it himself. The architect designs it. The tech can perform documented solutions

  • What programming language? You might have to back to basics. I know what you mean though. That was my frustration as well. The basics aren’t covered well enough on many courses, and learning in a browser IDE adds anxiety when following tutorials if you don’t know how to set up your environment.

    If it’s with Python, maybe I can help. Getting your environment set up is the most important part. I like to use pycharm, it forces you into virtual environments but that’s a good practice to follow and gives you plenty of practice with the basics since you’ll have to install your dependencies for every project.

    Sometimes the dependencies change, and it’s nice to know what version you previously used vs how the new package version works.

  • I worked as a network engineer and got pretty frustrated working with outdated applications that were not user friendly. Once I became a supervisor, a large part of my job became writing and generating reports summarizing events that happened on the network that no one would ever read. I wanted to learn programming to automate the things I hated about my job.

    I’m still an engineer, not a developer, but I enjoy writing user focused programs that reduce or eliminate worker frustration. As with many jobs, it’s not the networking that’s difficult, it’s all the other bullshit you have to do.

    Also, learning how to parse, model and visualize data can really help you make your point to your management and get your ideas pushed through. Also a great way to earn brownie points with your bosses, as managers tend to love graphs.

    Wish I could say it was a passion for me but I really learned out of necessity.

  • Yeah, in my case, the decision to hire me had been made, but HR would of course onboard me. I got kind of blindsided as the person who asked me wasn’t the person who would be making the decision, she was basically a proxy. I asked what the range was and I got some generic “it depends”… I checked most of the boxes for skills but I don’t have a degree and for some reason that’s off-putting to large companies. Anyways yeah it didn’t feel right to be pushy so early