[saluki]

I made the switch from civil engineer to full stack developer in my thirties.

I knew some HTML, CSS and PHP and had been setting up websites for family and friends. I started freelancing in addition to my day job. Moved to creating PHP web applications and taking on more and more advanced work.

I slowly picked up larger projects, better clients until I got to the point where I was freelancing full time. Now I have a few clients that keep me busy working remotely. I have had a few contract positions 3 to 6 months at a time but mainly it's been freelance since I made the switch.

It's lots of work, you're constantly learning and trying new things. If you enjoy that and have a knack for programming go for it.

I have interviewed with some local companies I wouldn't say I was passed over for younger employees, mainly just not a good fit not enough experience. I can see where some companies would prefer younger candidates.

I would say GO FOR IT but maybe learn/get back in the game by freelancing/keeping your day job. Unless you can afford to quit your day job during the transition.

I would also recommend learning full stack instead of just focussing on front end, it's becoming more blended anyway. Front end is moving toward React, Angular, and Vue.js and is as complex more tightly coupled to the backend.

Also I would focus on learning Laravel (PHP) or Rails (Ruby) I think these are higher paying with more job openings/interesting projects.

Laravel has a great ecosystem, check out LaraCasts.com.

Rails is great as well.

Good Luck with the transition.

[mfalcon]

May I ask why you made that kind of switch? I'm a SW Engineer and I always liked the idea of being a civil eng.

[saluki]

I always enjoyed programming, was fascinated with startups, technology and SaaS so it was something interesting so I started building websites and then web applications while working as a civil engineer.

I enjoyed civil engineering too, but there wasn't a lot of room for innovation, lots of things are cookie cutter in civil engineering, there is some room for creativity but not like developing web applications.

I did develop two software add-ons for Civil 3D that were released by Autodesk that gave me a taste of software development.

Oh yeah there was also the slight economic collapse where all development and construction stopped, civil engineering firms cut 75% of their staff and salaries stalled and shrank. So it wasn't really a choice I was just lucky I had the skills in place to make the leap over to software development. It wasn't easy but I'm much happier as a developer.

[nashashmi]

Going from a civil engineer to computers and programming is an all too common career path. For some reason, even though I am very knowledgeable of computers/programming/development, I never made the switch.

Part of the reason Civil Engineers go into Civil is because they are excited by the idea of making things (especially with computers). Part of the reason they leave, is after they see how frustratingly slow-paced it is, how poor communication is, and how ridiculous the number of times your project or work gets axed (not shelfed, axed!).

There is a concept in software engineering called reusable code. That concept is completely absent from CE. The entire industry works that way. And it seems backwards.

I am still holding out hope that one day this field will improve, and I may have a hand in it. But in all honesty, I see architects, surveyors, and software engineers doing a better job of revamping this industry than civil engineers ever can.

[tonyedgecombe]

To be honest I think you can find those sort of criticisms in just about any industry, you can certainly find them in the software world.

[sidibe]

Also CE->SWE here, if you are criticising these issues in the software world you will hate being a civil engineer. While they are in some corners of software development, it's basically all there is in civil engineering.

Civil engineering is already figured out. In the first world, what you are supposed to do for most situations is not only almost entirely mapped out but is actual regulations. That's great for society, but there is just no stimulation for CEs. In the first world, being a civil engineer is mostly about knowing and keeping up with the the rules (which is a feat in itself considering how many organizations are involved and how scattered the information is), applying them, sending drafts to clients/regulators/etc. and waiting for weeks for responses.

[nashashmi]

Wow! You just brought back memories of a line in a paper I wrote my first week in Civil Engineering college ... "a boring field that is 1000 years old where all opportunities of innovation has already occurred". But when I was thinking of going into CoE or CS the dot com bubble burst and I had to reconsider.