101–110 of 176 posts
1. Waterfall is a cycle time of weeks
2. Agile is a cycle time of days
3. DevOps is the same cycle time as agile but delivering the the user instead of just showing a demo at the end of a sprint.
Earlier quoted context omitted.
Terraform is okay , if you don't value things like "loops that aren't an awful hack", but in 2019 Pulumi is significantly better and their cloud-agnostic implementation actually kinda works okay.
Pulumi would be perfect if the community edition was simply self hosted without support vs free with a single user only. At a stingy small org, I have no hope of ever using it instead of simply installing Terraform when the starter edition excludes secrets management and the API.
Earlier quoted context omitted.
My experience of that which has been called 'agile' is that it's an excuse by programmers not to do the boring stuff, so they can got straight into the coding. Not to plan, or even think too much, definitely not to document (sometimes not write anything down at all ), often not to test except in a token form and sometimes not even that. Is that agile? That's how 'agile' has been done where I work anyway. Maybe I've b…
Yes, I understand. While I’ve never only attributed that to Agile alone, but also this sort of brogrammer-code-is-the-real-product, it sometimes feels like a maturing industry sort of rolled back into its teenage years. Diagrams? Solution models (up front thinking)? Document for future reference? Nah, we don’t want to do that. It’s sad. Just recently had an experience like this with developers I manage. I do loathe t…
Beautiful description! That is so on the nail.
Earlier quoted context omitted.
In the 90's and 00's I was responsible for maybe 20-30 servers, now I am responsible for somewhere around the 2000 mark.. While "oh but you can't do that, that's not Infrastructure as Code!" sounds lame, and your co-worker should learn to be a better communicator, things need to be reproducible when working with more complex systems and that calls for more rigorous review practices. Please consider this: It's our pag…
In my experience ops call the developers when something breaks overnight in any case.
Usually I can just revert to an earlier version and file a bug report, sometimes I have to cherry pick.
Having developers "fix" things in production under time-stress at 3am without proper code review sounds like extremely poor practice.
Earlier quoted context omitted.
How is Devops "blue collar work"? Provisioning servers, databases, load balancers, etc and other resources use to involve someone driving down to the colo and installing hardware. Often now, it's a yaml file you run through Cloud Formation. Devops is just as much development and software engineering when you are working in a cloud environment -- it's an API call.
That's exactly the reason. Software engineering is about writing code, devops is about writing yaml files and keying into functionality that was implemented by software engineers.
i deploy all our cloud instances using Ansible (yml files) and I wouldn't have a hope of doing that if I didn't understand the OS I'm configuring with it (Linux).
I might see your point if you're talking about the yml that is used to configure 'value added' products from cloud vendors, but I avoid those like the expensive handcuffs that they are.
Earlier quoted context omitted.
That's exactly the reason. Software engineering is about writing code, devops is about writing yaml files and keying into functionality that was implemented by software engineers.
Dude, the yaml files I'm writing require good knowledge of the system they are configuring. i deploy all our cloud instances using Ansible (yml files) and I wouldn't have a hope of doing that if I didn't understand the OS I'm configuring with it (Linux). I might see your point if you're talking about the yml that is used to configure 'value added' products from cloud vendors, but I avoid those like the expensive hand…
Earlier quoted context omitted.
Pulumi would be perfect if the community edition was simply self hosted without support vs free with a single user only. At a stingy small org, I have no hope of ever using it instead of simply installing Terraform when the starter edition excludes secrets management and the API.
It's a bit rocky and I've been filing bugs to help, but S3 state support is strictly no worse than Terraform's and supports secrets just fine.
This article was frustrating to me. When it started out in the mid-90s (which is when I started my career also), I thought our experiences would be more aligned. However, I've never worked with an operations team. In all the places I've worked I've been expected to do everything from setting up servers (originally physical servers, later cloud servers), hardening them, installing software, optimizing the software, in…
"Devops" means not fighting with those people??? haha
Earlier quoted context omitted.
It's a bit rocky and I've been filing bugs to help, but S3 state support is strictly no worse than Terraform's and supports secrets just fine.
That's good to hear! Admittedly the main issue for us is convincing others that 1 user at $50/month is justifiable.