Interviewing Again
2023 edition
What It Seems I Need To Learn
-
Systems at scale, hardware and software. Being limited to experience of teams of 2 to 5 means I have not been exposed to antire universe of technologies designed around hard won best practices. Not that I’d need to make every project a composed cluster of resource consumption, but knowing more what to look for and seeing the hiccups at orders of magnitudes (100 developers, 1000, 10000) would be invaluable.
-
- Kubernetes local to cloud for every project. A committment to hardware ‘agnostic’, scalable, development and tooling from the beginning.
-
- Organizing work in projects. Keep up with PM tools. I am a PMP. IBM moving on from Rational DOORs is probably a big deal to a lot of people. Be great to work on a system that collected requirements at that level.
-
Frontends if for nothing else than quick tooling, demos, and a better portfolio (not to mention the company I hope to start.) I’ve worked in React, Angular, and now Vue. Getting beyond small updates to quickly building independently deployed frontends. User interfaces are pretty critical in system use.
-
- Build frontend for IVECS system in Vue. Deploy locally via kubernetes. Scale entire system to GKE.
-
Go – Python. Getting better at Go and python and fusing the two.
-
- Identifying when to transition from JIT to typed/compiled is tough. I think the decisions around performance and cost make more sense at scale. It may be that developing as part of a larger group in a more involved system will make me better at both languages to some extent.
Whether It’s Worth Studying For Fun Formally (ASK CHATGPT)
Part of my new creed is trying not to give advice I’m not paid for and not qualified to give. I’m horrible and going through an everything is a question phase. Giving advice is serious business. I often think the power of appearing expert is abused. Above is my expert opinion about myself. Developed from a mountain of rejection, job descriptions, and my own project needs. What does ChatGPT think?
Prompt: “Is it worth studying? If so, how should I focus based on current trends and requirements in the systems hardware and software industries?”
Yes, it is worth studying the areas you mentioned. Here are some suggestions on how you can focus based on current trends and requirements in the systems hardware and software industries:
Systems at scale: You can focus on learning more about cloud-native architectures, containerization and orchestration, and distributed systems. Familiarizing yourself with technologies like Kubernetes and GKE can be valuable.
Project management tools: Consider learning about agile methodologies and popular project management tools like Jira, Trello, and Asana. Focus on understanding how to manage projects effectively, especially in a fast-paced and rapidly evolving technology industry.
Frontends: Continue to develop your skills in modern frontend frameworks like Vue and React. Also, consider learning about design principles and user experience (UX) design to make sure that your frontends are not just functional but also visually appealing.
Go and Python: To get better at Go and Python, consider working on real-world projects that use these languages. Focus on understanding the strengths and weaknesses of each language and how to choose the appropriate language for different projects based on performance and cost considerations.
Overall, it's important to continue to learn and stay updated on the latest industry trends and technologies. Networking with professionals in your field and participating in online communities and forums can also be beneficial.
I’ve gotten and given worse advice, I think. Maybe I like the fact that ChatGPT seems to be biased to kiss ass haha.
References
Extra Images
