CI/CD 101: Having a proper state of mind
[Part II]

For me, CI is more than just a tool. Like a hammer. It’s about collaboration and process. CI is blurring the line between 2 tables and 2 different persons(maybe more): code reviewer and developer. 

Sometimes developers wanna break things. It's a part of their job. But pretty often, when the system goes down = developer feeling bad about it.

Yes, most developers take it personally.

This is why being a developer is a pretty hard job. If you didn't realize it before -> go and hug one of your teammates, they will appreciate it, especially on Friday.

✳️  Developers don't like it when their code has errors

Especially when they are in a hurry or have a tight deadline. Are you building custom stuff and have deadlines? OMG. sorry to hear that...

Any helpful gesture is appreciated. Always. It can be a nice word, a warm cup of coffee or one good meme that will reduce some stress. Help your developers, they working very hard.

  

When developers realize that the build does not 'compute' that works against them - everything changes. Using CI makes developers feel more secure and more comfortable.

Well, as a Dev, I like CI. Because robots do work for me and I benefit from it. Let's do more robots, more services that helping organize CI process and we, humanity, can focus on developing rockets or on science
 

Plus it adds extra perks like rules, any type of linting, etc. Building DevOps workflows can help teammates better understand how software and processes should work. It's a really cool direction software development is going right now.

Usually, the code reviewer(team leader) is pretty busy. Like our CPO. Instead of trying to debug new pull requests in his head - you see one simple message: build failed & x tests didn't pass.
 

It's a good sign for you, because you see a moment, when a system, that was build & configured just to save you from different problems.

As a dev, engineer, I like to play in automation. Or something similar. We are not just gears in a company engine. Sometimes, when the days are gray and it’s cold outside, we wanna play & chat.

And when we can set up a process that can organize our coding chaos. It’s very rewarding.

Check out this newsletter's sponsor - Circle CI. If you watch YouTube, you should remember that voice - "You have to try to build something, something great, something that matters...".

Circle CI can help you to set up workflows, enable debugging during builds, automate your tests and send you notifications when everything is done. You will be up-to-date with build results and can push your commits with confidence. Even on Fridays.

Btw, We have great stories from Hackernoon team(follow the yellow color):

- Linh talking about fundraising

- Natasha exploring new music

- Daria presenting recent crypto-podcast

- Austin trying to hack his brain

- Dane excited how annotation can change how people will read stories

- David summarising 2019 year for Hackernoon company

- Arthur promoting Ukrainian meals

🗯️[BREAKING] annotations + in-line comments are now in live beta on @hackernoon—we’ve implemented GUN’s decentralized database to power collaborative annotations on all stories. 💬read all about it in Coindesk, Bitcoin Exchange, and from our new contributor Ann O'Tations.

If you have a few (or many) experiences to share, you can become a contributor on Hacker Noon too.

Simply create an account, and join 10,000+ contributors sharing their knowledge and expertise with the rest of us. 

Maybe you'll get featured on our next newsletter too.

Until then...