1,211 karma · joined April 22, 2015
I found that most people focus on size and forget about reuse.
Sure, each layer adds size to your final image, but you can reuse them, so that you don't need to transfer the complete image but just the layers on top of the one that changed.
Flatten everything and you need to ship the whole stuff.
I don't know whether to laugh or to cry.
While it makes a lot of sense for Google, I have no reason to use it if I'm not a Googler (and even then).
How do I know? Well, I've been in such a spot. I've deeply considered whether to stay until retirement being paid a lot to be bored or be less paid in a more fun job. I chose the latter but I do not judge you.
In the context of this post, I wanted to check how much work the Spring team had done so I did the trial-error-fix process on purpose.
On real-world applications, I suggest you use the Java agent that comes from GraalVM and go into every corner of your application. At runtime, the agent will record every interaction and at shutdown, will write all necessary configuration files.
You can check the documentation here: https://www.graalvm.org/reference-manual/native-image/BuildC...
I've always wondered why most developers (myself included) prefer to follow popular opinions instead of thinking by themselves.
This post just frames what I've experienced in two decades of working in IT.
Would you mind being more precise?
I don't find the rollback announcement again, but I distinctively remember the fact I stated.
Mainly Java as I was a Java developer when I started Now a lot of Kotlin, Spring Boot, Kubernetes, Testing, ...
As a French native speaker, "Hell is other people" is indeed how I'd have translated it myself.
Next week, I actually need to write the damn piece ;-)
And thanks for your feedback btw.
That's a f... up conclusion if there's one. Let's look at it another way: in those private colleges, you'll likely find more students whose parents are rich than in public colleges. Guess what? After 40 years, there's a higher chance they will find themselves higher in the food chain than students from poorer families.
The only conclusion is the renewal of the capital gap generation after generation.
Well, live and learn.
Nope, he was right. DevOps is all and only about removing the wall between Dev and Ops. That might go as far as merging the team, but not necessarily.
However, the conference is _dead wrong_ is they convey the feeling that "DevOps is Ops with new tools". That's akin to putting lipstick on a pig, and does DevOps as an organization tool a lot of wrong (just like Agile, etc.).
So, in order to avoid bias on the reader part, I preferred to explicitly tell it was not trolling.
There is not such thing as "bad" or "good" in absolute. There are paradigmes that work better in certain contexts - and I use the word "context" in very general way here - and some that work worse.
If my consulting experience has taught me something, is that "it depends" is a valid comment most of the time. By the way, I also learned that if you stopped at this comment, you're not a good consultant.
Wow. Has the author any real-world experience from using micro-services? Or is it just word-of-mouth? Because I have a complete different take on this.
Explosive Kitten: fast-paced card playing games. A lot of randomness, but great fun
Evolution, the origin of species: just played it once, but I liked it a lot. Everything is about card combination
Unstable unicorns: another card game, the goal is to reach a stable of seven unicorns. Each round, one can add a new unicorn to one's stable, if one has a unicorn card. Of course, interventions by other players will make it hard to win the game