Amazon S3 will no longer charge for several HTTP error codes
Amazon S3 will make a change so unauthorized requests that customers did not initiate are free of charge. With this change, bu... https://t.co/TzsK7qbcS8
What I find the most depressing about this isn't even that much Linus' style of communication itself, but the fact that still so many people consider it ok and say "sometimes that is needed". No, it is not. There's so many more respectful and effective ways of providing feedback.
I'm not a fan of declarative / configuration languages but Pkl (https://t.co/ALMMBANr51) does look like a decent option, covering many of my usual complaints.
I definitely gotta give it a try. Also, know any experts / creators? Connect me so I can get them on @HappyPathProg.
What's a "best practice"? It's a procedure known to yield the best results for a given situation and desired outcome.
There are no general best practices because no practice is always best. E.g. Best practices don't exist for unknown unknowns. Knowledge and experience required.
The world would be a much better place if every programmer used the Tell-Don't-Ask principle. That means to do this:
quote.extendExpirationBy(days);
Not this:
LocalDateTime dt = quote.getExpirationDateTime();
dt = dt.plusDays(daysToAdd);
quote.setExpirationDateTime(dt);
Java Startup: Not From Scratch Anymore, with CRaC
Java 21 introduces a feature that lets your applications start up and reach peak performance instantly, and Spring makes this feature very easy to use. (follow thread --> )
Honestly I hate Utils* classes as much as the next developer, but half of mine are just variants of methods that rethrow checked exceptions as RuntimeExceptions
Spring Framework 6.1 is released! 🎉
https://t.co/xL3xj5IZ6m
Congrats to the @springcentral team!
6.1 is a foundation for Spring Boot 3.2 that will be released on the 23rd of November. It comes with quite a few exciting changes that i'll briefly explain here (1/7)
Spring Boot 3.2 introduces @ConditionalOnThreading - very convenient to decide which bean should be create beans only if Java 21 virtual threads are enabled
https://t.co/xbEaXfx8yX
This Drive is a Goldmine of AWS Certification Free Resources.
Discover the following Free and much more!
- AWS Certified Solutions Architect
- AWS Certified Developer
- AWS Certified SysOps
- AWS Certified Cloud Practitioner
- AWS Certified Solution Architect
- AWS Certified Developer
- AWS Certified SysOps Administrator
- AWS Certified Advanced Networking
- AWS Certified Security
- AWS Certified Big Data
And much more.
For the latest tech knowledge, updates, and career growth insights, make sure to 'Like,' 'Repost,' and Follow @ZabihullahAtal for an extraordinary journey in the world of technology!
Drive link:
https://t.co/9fB4vVGvaS
#AWS #AWSCERTIFICATION
📺 The recording of my session "Change Data Capture for Microservices" from @qconlondon earlier this year is online now, including a full transcript. Outbox pattern, strangler fig pattern, managing operational concerns--this talk has it all 🤓!
https://t.co/aN5ca2XQ5x
Interesting Java ☕️ library: JVector (https://t.co/yPUunRTvdk) is a zero-dependency, embedded vector search engine 10x faster than Lucene for large data sets
Spring Boot Database Admin scans your @Entity classes and automatically builds a web UI with CRUD operations for your database schema. Let's try it 👉 https://t.co/wpgF9U6QOg
What if you could choose the best node for your Kubernetes cluster before writing any code?
Imagine being able to estimate:
- Utilization.
- Overcommitment.
- Wasted resources.
- Costs.
And compare the results for multiple setups.
Let me show you how.
Scrum is a cancer.
I've been writing software for 25 years, and nothing renders a software team useless like Scrum does.
Some anecdotes:
1. They tried to convince me that Poker is a planning tool, not a game.
2. If you want to be more efficient, you must add process, not remove it. They had us attending the "ceremonies," a fancy name for a buttload of meetings: stand-ups, groomings, planning, retrospectives, and Scrum of Scrums. We spent more time talking than doing.
3. We prohibited laptops in meetings. We had to stand. We passed a ball around to keep everyone paying attention.
4. We spent more time estimating story points than writing software. Story points measure complexity, not time, but we had to decide how many story points fit in a sprint.
5. I had to use t-shirt sizes to estimate software.
6. We measured how much it cost to deliver one story point and then wrote contracts where clients paid for a package of "500 story points."
7. Management lost it when they found that 500 story points in one project weren't the same as 500 story points on another project. We had many meetings to fix this.
8. Imagine having a manager, a scrum master, a product owner, and a tech lead. You had to answer to all of them and none simultaneously.
9. We paid people who told us whether we were "burning down points" fast enough. Weren't story points about complexity instead of time? Never mind.
I believe in Agile, but this ain't agile.
We brought professional Scrum trainers. We paid people from our team to get certified. We tried Scrum this way and that other way. We spent years doing it.
The result was always the same: It didn't work.
Scrum is a cancer that will eat your development team. Scrum is not for developers; it's another tool for managers to feel they are in control.
But the best about Scrum are those who look you in the eye and tell you: "If it doesn't work for you, you are doing it wrong. Scrum is anything that works for your team."
Sure it is.
Thinking in Systems is the best book I’ve read all year. Feels like I gained 10 IQ points just by opening it.
Having clarity over how the world works is essential for anyone trying to do anything worthwhile.