David

500 : Brain general failure

Codemonkey

[David @davidfrigola]

procrastination is evil #focus

[nixCraft 🐧 @nixcraft]

Scumbag crontab. At least on two times I messed up https://t.co/3fXSiOm9OV #linux #unix #freebsd #macos

[nixCraft 🐧 @nixcraft]

modern work 😂

[Josh @joshmanders]

As a FAANG hiring manager, when I see a developer resume I throw it right in the discard pile.

To me, it's a red flag, if you're so good why do you not already have a job?

[GeeksCAT @Geeks_CAT]

Ja és oficial! 🚀 La tercera edició de la Festa de l'Open Source a Girona ja és una realitat i se celebrarà el dissabte 21 d'octubre. 🥳 No deixis passar l'oportunitat, reserva ja la teva entrada abans que els tallers esgotin les places ➡️ https://t.co/8C8l7O1T90

[Mario Fusco @mariofusco]

... and that's why loose coupling is an important design principle

[The Linux Foundation @linuxfoundation]

We are excited to announce the launch of OpenTofu, an open source alternative to Terraform's widely used infrastructure as code provisioning tool.

Read the announcement:
https://t.co/Ju0d6Fq190
#opensource #opentofu #ossummit

[David @davidfrigola]

@zinkiki 4

[Cory House @housecor]

4 software delivery metrics worth tracking:

1. Change lead time - How long does it take to go from code committed to prod?

2. Deployment frequency - How often do you deploy to prod?

3. Change fail rate - What percent of prod changes are broken?

4. Time to restore service - How long does it take to restore service when something fails?

[Piotr Mińkowski @piotr_minkowski]

Kubernetes Java Tip 💡

Do you set a CPU limit for Java☕️ apps on Kubernetes? How does it impact your apps startup time? You can solve that problem with a new Kubernetes feature called "In-place Pod Vertical Scaling" in that way 👇

#kubernetes #java #cpu

[David @davidfrigola]

@alex_esteve

[tom ��� @tom_antok]

Microservices architecture

[Programming Wisdom @CodeWisdom]

"What one programmer can do in one month, two programmers can do in two months." - Fred Brooks

[Vaughn Vernon @VaughnVernon]

A common misunderstanding about technical debt is that it's incurred by releasing "bad code." That's incorrect. It's a metaphor for releasing a model that you know is wrong based on new knowledge. The team releases with debt in order to receive feedback earlier than if time were taken to improve the model immediately. (You'd probably rarely/never release.) Still, the model can't remain wrong, or the team will continuously stumble over it. As concepts grow, the model will cascade into deeper debt, eventually making it impossible to bring into harmony with increasing knowledge. Soon, it's bankrupt.

Bad code is a different problem, making the model difficult to understand, correct, and improve, eventually leading to full entropy.

[David @davidfrigola]

@alex_esteve Poco paso veo ahí

[David @davidfrigola]

@alex_esteve Tree times

[Orange Bank España @OrangeBankES]

Ya puedes acceder a tu app de Orange Banky operar con normalidad. Esta incidencia no ha afectado a la seguridad de los sistemas, ni a tu dinero.
Hemos trabajado muy intensamente para resolverla, aunque nos ha llevado más tiempo de lo que nos hubiera gustado.

[Orange Bank España @OrangeBankES]

Estamos sufriendo una incidencia técnica que impide que accedas con normalidad a la app. Dicha incidencia no afecta de ninguna forma la seguridad de los sistemas, ni tu dinero.

Puedes seguir pagando con tu tarjeta de débito en establecimientos y recibir transferencias o Bizum.

[Orange Bank España @OrangeBankES]

Lamentablemente no puedes entrar en la app y realizar compras en e-commerce.

Hemos localizado el origen de la incidencia y estamos trabajando intensamente para restablecer el acceso a la app en la mayor brevedad.

Entendemos los inconvenientes causados y te pedimos disculpas.

[David @davidfrigola]

@alex_esteve B

[Paolo Patierno @ppatierno]

TopicGC: How LinkedIn cleans up unused metadata for its Kafka clusters https://t.co/20EOg8crD7