4 ms·

I switched from being an architect to a programmer at around 30. It really worked for me, I definitely had an aptitude for programming. Its also very easy to l

I switched from being an architect to a programmer at around 30. It really worked for me, I definitely had an aptitude for programming. Its also very easy to learn nowadays. You can learn on your own via things like this.. https://www.codecademy.com/learn/introduction-to-javascript https://www.codecademy.com/learn/introduction-to-javascript I think a good 1st step would be to do lots of tutorials like that in your spare time. See if you have an affinity for it. You should also think about what sort of stuff do you want to make. Programming is just a means to an end. What do you want to do with it? Websites? Mobile apps? I personally got into making games, which is a niche area but after a lot of rumination I clearly decided thats the area I wanted to work in. .... As for the next steps.. If you have any ideas for any little apps (like stuff you could use in your day to day life) you could build them in your spare time. Start building up a portfolio of your own projects. Once you have some examples of your work, you could start looking for a job, theres a global shortage of good programmers atm, so in more pragmatic companies, qualifications are not necessary. If thats not working out in your area, then you could do some part-time or online courses to get some kind of qualification. I do recommend getting a job somewhere (or a few places) before starting your own business. You will learn a lot about the software biz the 1st few years all while getting paid for it. Even if the company is terrible you will learn what not do to. Anyway imo the most important step is the 1st one. Learn how to code in your spare time, mess around with it, see if you like it.

galfarragem 8y ago
I'm also an architect switching to programming but I didn't finish the process yet. Apparently disconected both subjects have a large common ground: creating a machine from small building blocks. What I've found particularly difficult is to let go the past because I like Architecture and invested a lot on it. By the other hand, Architecture as a job is terrible, and that was the trigger to adapt my career.
- everyone 8y ago
  Cool! Yeah, I agree architecture often sucks in practice. I was not even a good fit. I was way too engineer / pragmatically minded, and I have a good bit of disdain for superficiality. You might notice that you're much better than your programmer peers at actual software architecture. Organising the software into some sort of structure or hierarchy that makes sense. Though after a while you might also realise that its better to avoid explicit structure in your software, if you can. If you try and really actually implement the fundamentals in your code all the time (tiny classes, tiny methods, avoid coupling, avoid duplication) your work will be very pleasant.

galfarragem 8y ago

I'm also an architect switching to programming but I didn't finish the process yet. Apparently disconected both subjects have a large common ground: creating a machine from small building blocks. What I've found particularly difficult is to let go the past because I like Architecture and invested a lot on it. By the other hand, Architecture as a job is terrible, and that was the trigger to adapt my career.

everyone 8y ago
Cool! Yeah, I agree architecture often sucks in practice. I was not even a good fit. I was way too engineer / pragmatically minded, and I have a good bit of disdain for superficiality. You might notice that you're much better than your programmer peers at actual software architecture. Organising the software into some sort of structure or hierarchy that makes sense. Though after a while you might also realise that its better to avoid explicit structure in your software, if you can. If you try and really actually implement the fundamentals in your code all the time (tiny classes, tiny methods, avoid coupling, avoid duplication) your work will be very pleasant.