31–40 of 85 posts
I was also in a similar position as you as a valued lead dev with 15 years of experience working in a company that didn’t want to embrace newer technologies (stuck on WebForms, not moving to MVC, etc). I was not interested in progressing into middle management and had hit the ceiling with regards pay so I became a contractor. I taught myself MVC got an initial bum-on-a-seat noddy contract which was doing MVC CRUD scr…
Chances are, you will be successful and unhappy at the next job.
You might be interested in https://info.covermymeds.com/ruby/ Ruby on Rails opportunity for java and .net developers; note:I am not affiliated with covermymeds, heard about it on the Ruby Rogues podcast.
What I hear is that you have been successful (or think you have been) in quite a few different things which you didn't really want to do. Chances are, you will be successful and unhappy at the next job.
Earlier quoted context omitted.
To add onto this, being a "developer DBA" can be clutch. OP has a background in application programming and can relate to other groups a lot easier and inherently understand pain points and reasoning behind certain architecture decisions.
As a young-ish developer mostly interested in database and backend work, what skills/path would you say is necessary to function in a full-fledged DBA role? I'm finding in my contracting work that my database skills are above-average and usually one of the big things that I'm relied upon for and I think this is worth pursuing.
I'm in a somewhat similar boat in that I've too much developer experience to be a junior programmer but not as much experience in modern stacks (I've about 5 years on modern web dev but two of that was mostly Drupal) before that it was all line-of-business internal stuff for business. I solved that problem by bootstrapping a startup with consulting/development for other startups that are viable but weak technically,…
I have a bootstrapped project already, but as you probably can infer in my postings, I'm not good at sales. I'm toying around with finding a business partner and maybe get more out of it. Side projects will probably always be a part of what I do, but I really want to find something to replace the 9-6 I have now.
That might be a good way to go.
Earlier quoted context omitted.
To add onto this, being a "developer DBA" can be clutch. OP has a background in application programming and can relate to other groups a lot easier and inherently understand pain points and reasoning behind certain architecture decisions.
As a young-ish developer mostly interested in database and backend work, what skills/path would you say is necessary to function in a full-fledged DBA role? I'm finding in my contracting work that my database skills are above-average and usually one of the big things that I'm relied upon for and I think this is worth pursuing.
Then again, maybe DBAs aren't as bogged down by the minutiae in some places and have more of an ability to troubshoot and resolve DB code/structure problems. It always seems like that's their job but they never have enough time to properly do it with the myriad of other requests.