Andrzej Winecki

Part-time monkey, part-time maker of computer stuffs. 🐒 🤖

[Andrzej Winecki @andywine_io]

Wondering about this year's State of Devs 2026 survey results. Lots of culture-centered questions.

Take it if you have 5 minutes https://t.co/gwJpSbB0X4

[Andrzej Winecki @andywine_io]

@alexeyguzey hey Alexey this was a good post, now it’s 404 😅

[Andrzej Winecki @andywine_io]

@UntoolsHQ are you considering implementing Zwicky Box in the app section of Untools? Could be a cool addition ;) more info https://t.co/zTqcAptCHk

[Andrzej Winecki @andywine_io]

@flydotio I love your docs (https://t.co/KM9hR9bOrZ); the most functional and beautiful docs site I've seen in a while. Is that a custom-themed Docusaurus with Algolia search connected?

I want to build docs like these, too! <3

[Andrzej Winecki @andywine_io]

@rouanw I've been thinking about similar approach recently, revolving mostly around "Show" - I've even put some simple automation for this on GH, might interest you https://t.co/OZFa0Hase6.

Thanks for giving me a higher level conceptual framework for this!

[Andrzej Winecki @andywine_io]

It's possible to have both continuous integration and pull requests at the same time.

You only need trust.

I love how @rouanw put it:

"Ship / Show / Ask"

https://t.co/IO5J0VdnVq

[Andrzej Winecki @andywine_io]

As I've automated my company's accounting & reporting, I've observed this phenomenon:

I've learned Integromat — 1 full day
Created my first automation — 3 hours
Created my second automation — 1 hour
..
Created my recent Nth automation — 10m

[Andrzej Winecki @andywine_io]

I've been looking at this picture wrong for years.

What it misses is the fact that automation, like any other skill, can be developed and made more efficient.

[Andrzej Winecki @andywine_io]

By learning automation software and tricks, you will develop patterns that make further automation quicker, more robust, reliable, and maintainable.

[Andrzej Winecki @andywine_io]

@d_stepanovic Agree.

In a high trust team, a dev should be empowered to choose whether a change requires a blocking CR or not.

A while back I've made a little experiment on how to do non-blocking PRs using Github.

https://t.co/OZFa0Hase6

[Andrzej Winecki @andywine_io]

The bad: Expensive.

In our case, dyno were 3-6 times pricier than raw AWS EC2 instances (on-demand!). With reserved instances, it would be probably closer to 5-10x more.

[Andrzej Winecki @andywine_io]

We're migrating away from #heroku at @packhelpcom.

PaaS is a trade-off. You trade the infrastructure work for focus to direct into your product instead. It's a huge win at first.

I've wrote a post about our main pain points as we scale.

https://t.co/a2lK4ABVyH

[Andrzej Winecki @andywine_io]

The bad: Networking limitations.

- No 'pod' concept (hard to make 2 containers talk to each other)
- Without paying a premium, you can't choose datacenter (just broad EU or US)
- Apps accessible at <app>.herokuapp.com (ddos attack vector; you can't disable it)

[Andrzej Winecki @andywine_io]

@linuz90 Yeah, I'd probably go with video too. But I remember playing with APNG and a hack by SublimeText (https://t.co/zsfxTjTQA8). For animations with little changes, the ultimate sile size was ridiculously low. But it might be an overkill here 😅

[Andrzej Winecki @andywine_io]

Great piece by @BretFisher on DevOps fundamentals.

Also, a clear & simple #devops assessment, split into 3 categories: Culture, Process, Technology. Doable in 10 minutes.

https://t.co/0yRj5WTMoY

[Andrzej Winecki @andywine_io]

@miroslavcsonka @andrzejkrzywda @arkency Awesome! Did you do these post commit/merge reviews directly in Github (Projects) or did you use some additional tooling? Wondering if there's software dedicated to these practices.