4 ms·

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

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.