Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
Anybody think that it is worth getting very clued up on GDPR ready for this to come into play? Many big institutions both private and public will be very worried about this and it may become a top priority for them through contractors.
I thought about this but figured it would be mundane (well at least IMO) work helping companies achieve ISO 27001 and similar information security certifications + associated data clean up. I see a few companies trying to jump in on this with products but I think it'll be a very bespoke fix. Each company sprinkles / drops their customer data in places differently with a myriad of integrations and processes between their selected or hand rolled systems.
There are companies offering 'Consent Lifecycle Management' systems. Not sure how much of that is a fix vs a box ticking exercise for the legalities.
I'm sure there's money in it, just not sure if the effort / renumeration balance is appetising.
WRRTOP - I'm currently in my first DevOps contract, having come from a platform (VMware/Windows/Linux support/integration) contracting background. The initial learning curve was fairly steep, at least for me as a basic coder - (PowerShell/JavaScript/vRealize Automation Suite/Jenkins/Ansible/Jira etc) - but once you've picked up one scripting language, one tool of each type (e.g. config management with puppet/ansible) - you can pick up others fairly easily.
HTH
Now all you need to do is realise it's not all about tools
Anybody think that it is worth getting very clued up on GDPR ready for this to come into play? Many big institutions both private and public will be very worried about this and it may become a top priority for them through contractors.
Worth it in Britain? Well, maybe but it's only going to be for a fairly limited time due to Brexit, surely? I'd imagine most big British companies won't overly worry tbh - be subject to it for what, a year?
I'd suspect on a wider note there will be plenty of work in the next year or so due to Brexit...
Anybody think that it is worth getting very clued up on GDPR ready for this to come into play? Many big institutions both private and public will be very worried about this and it may become a top priority for them through contractors.
Surely the problem with DevOps is going to be, like Agile, vast numbers of companies wanting to adopt it ( current trend... ) and making a balls up of it due to lack of real tangible knowledge?
Normal length working days. A lot of freedom to examine problems and come up with the correct solutions, without too much red tape involved. Lots of discovery around currently manual processes and business pain points, coupled with a heap of pro-active automation of anything that was considered onerous, unreliable or time consuming, freeing up time for incumbents to lay off the "BAU" a bit and learn the same skills, and ultimately automating and mentoring myself out of a job (quite intentionally!).
DevOps isn't "fire fighting" and rebooting servers, it's working damn hard to prevent these issues from occurring in the first place, making code deployments a non-event, and embracing QA to get things right the first time, in a secure fashion.
This^
WRRTOP - I'm currently in my first DevOps contract, having come from a platform (VMware/Windows/Linux support/integration) contracting background. The initial learning curve was fairly steep, at least for me as a basic coder - (PowerShell/JavaScript/vRealize Automation Suite/Jenkins/Ansible/Jira etc) - but once you've picked up one scripting language, one tool of each type (e.g. config management with puppet/ansible) - you can pick up others fairly easily.
Does it make sense to retrain in these skills. Any members with these skills please share your experience.
I have none of those skills, does that mean I am doomed
Oh hang on I am not a code monkey so that is not really an issue, my theory has always been don't go for what is in demand now, try and work out what will be the next big demand and get there early. How that works with programming languages I don't know, it's why I have never had an interest in being a developer, too much to gamble (albeit with big pay offs if done right)
A lot of companies going through "digital transformation" atm, automating testing and deployments. I was championing DevOps practices (although not using the term internally, no weight with management - they just want to see project delivery go smoother and cheaper) for my last 2 years in my permie role.
Does require the company to be aligned top to bottom, went to DevOps Enterprise Summit in June, "Transformational Leadership" was this years recurring theme, and expanding DevSecOps to BizDevSecOps. Wonder what it'll grow to next year ...
Could you please elaborate on what your job entailed
Normal length working days. A lot of freedom to examine problems and come up with the correct solutions, without too much red tape involved. Lots of discovery around currently manual processes and business pain points, coupled with a heap of pro-active automation of anything that was considered onerous, unreliable or time consuming, freeing up time for incumbents to lay off the "BAU" a bit and learn the same skills, and ultimately automating and mentoring myself out of a job (quite intentionally!).
DevOps isn't "fire fighting" and rebooting servers, it's working damn hard to prevent these issues from occurring in the first place, making code deployments a non-event, and embracing QA to get things right the first time, in a secure fashion.
Leave a comment: