The worst thing about Jenkins is that it works (2019)

Drive shaft is a good analogy though because its not simply moving data (unless we’re getting really abstract).

> One of the mostly-false promises of Docker, as it was sold to me by the true believers who introduced me to it, was that, if you do it right, you can run the same docker image, and therefore have basically the same environment in production, in CI, and on your local development machine.

I literally have never worked anywhere that hasn't used the same container in dev/test/prod.

People who have had to deal with processes that rebuilt images for each environment, can you tell me what was different in each image?

I meant to make a blog post about this, but here's a good a place as any: GitLab absolutely innovated many hard parts of CI/CD as a platform-native piece, but it feels like they lose slightly to GitHub on what GitHub does best -- social virality for developers. The problem with losing slightly there is that the advantage compounds; if developers find it easy to make and share, then they make and share which makes more people make and share and generates tons of value for a platform.

It may not be safe, but being able to:

    - uses: some-developer/some-repo@some-branch

No one would accuse GitLab of being a "copy" in recent memory like they did in the bad old days, but IMHO they need to just copy the shit out of when GitHub gets social things (like this) right.

I put, however, that only companies have the problem, not programmers, and not even regular (sized) engineering teams; except when they have a fast employee turnover speed.

I do not have a very clear idea, but roughly speaking I'm saying that java does really well in the "too many engineers are working on the same code but not at the same time" problem space

Initial announcement, 2015: https://blog.jetbrains.com/blog/2015/09/03/introducing-jetbr...

Community anger a couple days later: https://bytecrafter.blogspot.com/2015/09/how-jetbrains-lost-...

Significant changes after hearing the feedback, a couple weeks later: https://blog.jetbrains.com/blog/2015/09/18/final-update-on-t...

I'd trust Jetbrains -- as a company with a few decades of experience serving devs and only devs -- much more than your typical get-rich-quick cloud SaaS startup that's just looking for a quick exit.

Yes, they need income too, but they're one of those few tech companies not aiming for hypergrowth, just a sustained user base.

Even though VScode gets all the love these days, and Atlassian and Github and CircleCI etc. get all the enterprise use, they've made some really cool products of their own too (Space, TeamCity). And their IDEs continue to be excellent.

It's not like TeamCity even has a secret catch... their cloud version DOES have a monthly cost already. It's only the self-hosted version that's free.