Johan Siebens

Cloud Architect / DevOps.

[Greg Young @gregyoung]

This is one of the most difficult lessons to learn.

[Work Chronicles @_workchronicles]

White Lies

[Anaïs Urlichs @urlichsanais]

Overengineering too early is the death of good systems.

[Jessie Frazelle @jessfraz]

I feel like 99% of being a software engineer is debugging random shit, 1% algorithms. As you gain experience you see more random shit, your random shit toolbox is ever expanding until you can figure out anything w time since it’s semi like something else in your toolbox.

[Eduardo Ferro @eferro]

"Code is liability. To build something is to be responsible for its existence, forever. Write more software only as a last resort." @mipsytipsy

[Jaana Dogan ヤナ ドガン @rakyll]

Working for incompetent people will make you incompetent regardless of your skill set in record time.

[Patrick Debois @patrickdebois]

you build , you ruin it

[Johan Siebens @nosceon]

This is such a gem!

[Charity Majors @mipsytipsy]

I just got back from @fintechdevcon in Austin. It was a super fun trip (notwithstanding the 105 degree air 🥵).

I gave a new talk while I was there, on why compliance and regulatory standards are ✨not✨ incompatible with modern development best practices.

[Jessie Frazelle @jessfraz]

There is no motivation to write code more than the sweet release of deleting a bunch of lines of really gross shitty code the new, clean code replaces

[Bartłomiej Płotka @bwplotka]

"Imaginary problems are the root of bad software"

https://t.co/dCSICwMUXX

[Alberto Brandolini @ziobrando]

Always funny to see how organizations that piled up bad legacy code in years are paralyzed choosing the perfect way to clean it up.

[Osman 🚀 @osmvn90]

“Writing code gets easier over time but building and maintaining software is always hard.”

– @kelseyhightower

[Charity Majors @mipsytipsy]

The single best thing you can do to improve your software quality and velocity, and find bugs early, is still this:

💀 instrument your code as you go
💀 run tests. get review.
💀 deploy asap
💀 look at your instrumentation. is it doing what you expect? anything look weird?

[Johan Siebens @nosceon]

Current status:

[poorly drawn lines @PDLComics]

what's wrong?

[Johan Siebens @nosceon]

"When you make architecture “someone else’s problem” and scrap the expectation that it is a core skill, you get weaker engineers and worse systems."

[Charity Majors @mipsytipsy]

I wrote a slightly longer-form piece about the risks of having an "architect" role distinct from engineering, and a few models for avoiding/compensating for that risk.

Thanks to all the wonderful architects who replied. (I 💜 you, I really do!!)

https://t.co/qrPUVZ3qso

[Charity Majors @mipsytipsy]

"Enterprise Cloud Architect". (Tell me you haven't written any code in a decade without telling me....)

But seriously. Effective architects (and they exist!) are typically,

a) grown from within, not hired from without

b) never more than a few years removed from building things

[Mario Fusco @mariofusco]

When you have to choose among readability, conciseness and performances always go with the first one by default and switch to the other two only if you have very good reasons to do so.

[Alex Ellis @alexellisuk]

My new style for rapid prototyping in @golang:

* All code goes in main.go, in main(), no extra methods, no packages, no extra files
* Use Go's flags and log packages
* Maybe create a few separate methods/files, still in the main package

For as long as possible..