Versatile software engineer with a background in .NET consulting and CMS development. Working on regaining my embedded development skills to get more involved with IoT opportunities.
Time and $ and sanity. I am the only dev at my current place of employment, inherited a build system which involves copying and pasting to PROD servers. The code is a mess to begin with, so I haven't been able to get it refactored into something that can be built in an automated fashion. None of my requests for tools get granted and I don't have any time to learn. I started playing around with Chef at home and it is pretty enjoyable, just a LOT to take in all at once.
I am getting ready to leave the company...I haven't endured several near death experiences throughout my life so that I can fix Web Forms applications and sit in meetings all day :D
Versatile software engineer with a background in .NET consulting and CMS development. Working on regaining my embedded development skills to get more involved with IoT opportunities.
You are correct. I think it is a mixture of two things though. The code quality creates a challenging situation: not sure how much you know about ASP.NET, but this site is an old website application where it doesn't have a project file, so it is more difficult to invoke MSBuild and a lot of templates for building .NET projects provided by build systems aren't applicable.
I also think that the demos and tutorials that are presented on DevOps are too simplistic and highlight ideal cases. Who knows, maybe it really is as easy as some of the demos make it seem. I just always seem to hit some edge case n one else encounters.
"...I am getting ready to leave the company...I haven't endured several near death experiences throughout my life so that I can fix Web Forms applications and sit in meetings all day :D" Good on you! No need to spean your life doing anything you do not enjoy.
If you like Chef, checkout Ansible, Puppet, and SaltStack for comparison.
Yes, seeing the differences will help, else these tools are a big mess because everyone just talks about the tools without even understanding the requirements.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Time and $ and sanity. I am the only dev at my current place of employment, inherited a build system which involves copying and pasting to PROD servers. The code is a mess to begin with, so I haven't been able to get it refactored into something that can be built in an automated fashion. None of my requests for tools get granted and I don't have any time to learn. I started playing around with Chef at home and it is pretty enjoyable, just a LOT to take in all at once.
I am getting ready to leave the company...I haven't endured several near death experiences throughout my life so that I can fix Web Forms applications and sit in meetings all day :D
And you are also talking about the bad quality and legacy code here if I am not wrong.
You are correct. I think it is a mixture of two things though. The code quality creates a challenging situation: not sure how much you know about ASP.NET, but this site is an old website application where it doesn't have a project file, so it is more difficult to invoke MSBuild and a lot of templates for building .NET projects provided by build systems aren't applicable.
I also think that the demos and tutorials that are presented on DevOps are too simplistic and highlight ideal cases. Who knows, maybe it really is as easy as some of the demos make it seem. I just always seem to hit some edge case n one else encounters.
"...I am getting ready to leave the company...I haven't endured several near death experiences throughout my life so that I can fix Web Forms applications and sit in meetings all day :D" Good on you! No need to spean your life doing anything you do not enjoy.
If you like Chef, checkout Ansible, Puppet, and SaltStack for comparison.
Yes, seeing the differences will help, else these tools are a big mess because everyone just talks about the tools without even understanding the requirements.