jobsearch

I've re-read it, and I would say I have the soft skills down for sure. I like to think I did well at translating business to engineering, collaboration intra- and interdepartmentally, sharing and explaining code. I do at least the engineering principles you've listed. It still stands I have a lot of things to check off your list. Thanks!

I haven't joined any meetups. I have work projects I can talk through, but nothing public-facing.

I think 'qodeninja nailed it on the head as for what I'm lacking. At this point I'm more of a hacker, someone who can put pieces together, rather than elegantly construct solutions. This comes quite quickly during the algorithm portion.

My strengths would be my quickness to adapt, and my ability to put together a myriad of technologies together. At my previous job I was able to switch between different development teams and get up to speed in short order. I created APIs, designed interfaces along with usability testing.

My weaknesses lie in the finesse. More algorithmic complex situations are tricky for me. Once I understand it, I can piece it together with existing solutions, but I would say my algorithm toolbox is pretty small.

Okay, I more than willing to take any old job. You're right on the timeline and rust. I've dusted off a fair bit by the end of these round of interviews, but I have a lot more to go. I think going this route makes a lot of sense. I just need to comb the market. Thanks!

Thanks! This is incredibly helpful and I wasn't aware of the distinction between developer and engineer in engineering land. I can see the first major steps you've listed is algorithms, algorithms, algorithms. I think you described me to a T in that I'm closer to a hacker than an engineer. I know a handful of what you've listed (e.g., REST, HTTP, pointers), but I've got my work cut out for me.

It's time to get out of the developer world. Thanks again!