Two things come to mind… my work and my involvement with FIRST robotics.
I’m the Director of IT Operations for a contract research organization (CRO). While that might not sound inherently interesting it’s deeply fulfilling. My role involves building and maintaining software that help facilitate critical research for NIH and NCI, often supporting breakthroughs in healthcare and science. I love the intersection of technology, problem-solving, and enabling teams to deliver life-changing results by helping change the standard of care for people affected by cancer.
Outside of work, I’m heavily involved with FIRST robotics, which is a worldwide competitive robotics program for high school age students. It’s an amazing initiative where students design, build, and program robots to compete in team-based challenges. And it’s very fun. I mentor students, guiding them through the technical challenges we come up against and help them discover their own potential. Watching young minds light up is very rewarding. Being a small part of that community is one of the most rewarding things I do.
I had a very similar line of reasoning one afternoon when making a salad for lunch. The fork, the plates, the kitchen, the ingredients, the electronics needed. All the details, history, effort, CAD, software, billing, logistics, sales, monetary transactions... which all led up to the moment where I could enjoy a salad.
After 10+ years working as a web developer with a non-CS degree, I heard about Georgia Tech's OMSCS program [0] and signed up almost immediately. The timing was right for me and my family and my employer offered tuition reimbursement. I kept my day job and spent nights and weekends working on assignments and studying. It was challenging and learned quite a bit.
A few years back before Covid, I held biweekly open meetings for anyone to learn practical Git basics where I work. I had about 20 people come through (PhD's, Statisticians, etc.) Let's talk! My email is in my profile.
If you truly want to learn, I suggest joining a local FRC Robotics team as a new/junior mentor. If you simply ask the students to show you what they have been working on, you may be inspired to join in and help. You'll learn together... mechanical, electrical, programming, etc.
I've been volunteering as a FIRST mentor for the last nine years and have learned more about robotics from the students than I did in my master's program or on my own.
I have benefited monetarily indirectly by lurking on HN for years and reading others’ thoughtful comments on a variety of subjects. Then apply some of those thoughts to my career as a developer, then later a EM. HN has been a gold mine of ideas by reading what others on HN post while interacting with each other.
For representing the technical architecture on a whiteboard, I tend to gravitate towards the first three levels of the C4model [0]. For meetings with management, I like to use AWS's architecture icons [1] within a slide deck.
I'm the technical lead for the IOTN [1] which is a part of the Cancer Moonshot program [2]. Our mission is to improve immunotherapy outcomes and to ultimately prevent cancer before it occurs. Our team is moving forward on a few projects internally that I'm not at liberty to share but will be released later this year. There is a lot of hope that immunotherapy will have a profound affect on patient outcomes.
Define the problem. Write some code to solve the problem. Ask people who have that particular problem to give you money. Ask them if they know others who have the same problem. Finally ask them if they have other problems you can solve. Then repeat.
The validation happens the moment you ask someone for money. You'll know either way quite quickly.
Do you have a blog post or could recommend one that covers your setup? Particularly any software that needs to be installed to get ML setup properly. I’m putting together an eGPU together in the near future and have read quite a bit, however any pitfalls that could be avoided would be helpful to know up front.
I’m the Director of IT Operations for a contract research organization (CRO). While that might not sound inherently interesting it’s deeply fulfilling. My role involves building and maintaining software that help facilitate critical research for NIH and NCI, often supporting breakthroughs in healthcare and science. I love the intersection of technology, problem-solving, and enabling teams to deliver life-changing results by helping change the standard of care for people affected by cancer.
Outside of work, I’m heavily involved with FIRST robotics, which is a worldwide competitive robotics program for high school age students. It’s an amazing initiative where students design, build, and program robots to compete in team-based challenges. And it’s very fun. I mentor students, guiding them through the technical challenges we come up against and help them discover their own potential. Watching young minds light up is very rewarding. Being a small part of that community is one of the most rewarding things I do.