DOES20

I hate the term software factory. its insulting both to software engineers and to factories.

"Lets put Resources on it", its people not resources!

@paula_thrasher Totally. Emergent Determinism.

Calling people resources. They are people.

I'm currently feeling grumpy about "modern applications"... it implies that everything which doesn't adhere completely to today's trends--I mean, best practices--is an "ancient application."

"capacity" It's not like it's a bucket with a certain number of hours. Focus, mix of activities, etc all matters when it comes to productivity and happiness.

@davidstanke Micro services has taken on a whole new meaning too unfortunately.

Most favorite: Maker. We are makers; we bring new products into the world through collaboration and creativity, through learning, caring, and safety.

I hate the term Hybrid cloud when used to mean "keep our data center but run one small app on AWS"

Least favourite: Velocity. Say/Do Ratio. Maturity Model. Resources.

(edited)

favorite term is Technical Debt. Its overused, but its so real. SO REAL.

@mickfeech Yeah, every customer I speak to has a huge monolith, and then "a handful of microservices that do some auxiliary things." So it's neither here nor there, and everyone's disappointed by it. :-(

@paula_thrasher Perfectly said. Look over here in this dark corner, we're agile we're cloud! (or whatever)

@paula_thrasher agree! All tech is debt, as learned from @davidstanke at devopsdays nyc! ;)

Favourite: Outcomes. Autonomy. Multi-disciplinary. Emergence.

Better Value Sooner Safer Happier

Elephant Carpaccio

@mrmarrocos Thanks for the plug! https://www.youtube.com/watch?v=EpPX6DXaGMg

Least favorite: Velocity. Never has a good idea been more abused and misused.

Favorite: Empathy (although we don't talk about it as often as we should).

@davidstanke Hybrid: To do two things badly

+: Psychological Safety

@jonsmart haha!

@jonsmart YES -- Supporting psychological safety is *proven* to make teams more effective. And I'm pretty sure it makes us better humans.

Favorite: Kaizen. It's never hard to get people to agree that we can always get better.

Favorite: learning, fast feedback

most favourite is. If you can't search over #google you can be good IT engineer :D #devops #does20

Listening is more important than talking. Reading [code] is more important than writing [code].

there is no one path to success, success comes from being flexible

Ask questions and if you don't feel comfortable asking questions take lots of notes. You come into companies with a new perspective, you see opportunities that many of us may not see anymore.

fastest growing field - "software is eating the world"

Never forget that you are making products for people. Real people with real lives, real needs and wants. Good products are products that make a difference to users. And they are made by makers that care about them.

Ask stupid questions before they become really stupid questions

@realMattKParker totally! listen to the customer, else you will get demoted from an employee to a customer

Seek out new perspectives. There's a lot to learn and seeing how different teams / companies / individuals do things is the fastest way to grow.

1) Don't stop learning; 2) Be multi talented; 3) Have integrity; 4) Be cool, things will fail; 5) Lab, lab, lab; 6) Scripting and automation; 7) Communication and soft skills.

it's not really a career in technology. It's a career in customer value, continuous improvement and people

What you're doing today will not be what you do for your whole career, nor will it define you. There is plenty of room to stumble, fall, and get back up again.

What ever your role is, no matter how small, seek to be excellent at that role.

@jonsmart well said :)

So many things but I'll pick 3: 1) you own your career & have both the right & responsibility to steer it; 2) choose to work for managers who are good advocates / champions; 3) titles do matter; don't believe anyone who tells you otherwise.

don't be afraid of the career pivot or stretch assignment, its the best way to learn.

respect actions, more than titles and hierarchy

take your time, do your apprenticeship, become an expert. Your future self will thank you when you are leading people (direct line or influence) when you've done their job

@jonsmart I like that a lot. Technology and process is easy, the real work is relating to people.

@testobsessed Re: titles. Earlier in my career I underestimated the extent to which my privilege allowed me to ignore such things. I believed titles didn't matter, opportunity did. I underestimated the extent to which title determines compensation & opportunities.

@Ben_Grinnell Don't let software eat the world. Let software support the world.

Assume positive intent

Wow, today I'm learning about the Radford compensation scale, how it can be abused, how it can be countered to protect your team, etc. Thanks @davemangot @testobsessed!

#technology has always driven the present & future and would always do. The more closely you are aligned to it and more secure the world & your career pat is #devops