2 ms·
So I'm a software engineer too, but also a cyclist. A weightweenie. At certain point, you begin to mix and match totally incompatible parts, solvable with a mod
by Klaster_1 5y ago
So I'm a software engineer too, but also a cyclist. A weightweenie. At certain point, you begin to mix and match totally incompatible parts, solvable with a modest manufacturing capability. For me, the learning path was basically the same as with programming - lots of motivation, access to internet and tools (a machinist). Back in school, we were taught part sketching and machining basics, which helped a bit. I picked FreeCAD out of available open source solutions, watched a lot of great tutorials on YouTube and, though trial and error, managed to produce designs good enough to serve the purpose. Machinist services in Russia are incredibly cheap, especially if they have their own machines in a garage. With small beginner projects, the price of error is just your time and materials, don't be afraid to experiment.
On a side note, my mechanical engineer acquaintance complains that he should have followed the CS route because programmers earn substantially more here. The grass is greener.
- Izikiel43 5y agoOr you can be this guy, who has a Bachelors in Mechanical engineering, a Masters in CS, and does crazy stuff: https://www.youtube.com/c/stuffmadehere https://www.youtube.com/c/stuffmadehere
- polishdude20 5y agoI'm like your acquaintance. Did mechanical engineering, worked for a few years and realized the jobs around here doing mech eng kinda suck and the pays bad. In software now and sure, it's not hands on as much as I'd like but I earn enough money now to live comfortably and work on my own projects at home in my free time. For me it was a priority shift. Earn more so I can provide for my family better and then use the rest to work on modest projects as hobbies. Or earn less so I can work on mechanical projects but not be able to provide the quality of life for my family I'd like.