cagatay
@cagataytanyildiz.com
Doğrusu ben de bu dertten muzdaribim. @seyfedd.in 'in şu iki yazısı çıktı halinde dosyalarım arasında duruyor. Arada sırada çıkarıp okuyarak kendime bir hatırlatma geçiyorum. Bu durum adete ağır bir yemek sonrası gelen miskinlik gibi. seyfedd.in/writing/mode...
Modern Çağın Laneti: Instant Gratification
En son ne zaman bir müzik albümünün çıkışını aylarca beklediniz? Ya da bir bilgisayar oyununun devamının geleceğini öğrendiğinizde geceleri hayalini kurarak uydunuz?
Bundan 2-3 sene kadar önce, yılla...
seyfedd.in
October 14, 2025 at 7:19 AM
Doğrusu ben de bu dertten muzdaribim. @seyfedd.in 'in şu iki yazısı çıktı halinde dosyalarım arasında duruyor. Arada sırada çıkarıp okuyarak kendime bir hatırlatma geçiyorum. Bu durum adete ağır bir yemek sonrası gelen miskinlik gibi. seyfedd.in/writing/mode...
Reposted by cagatay
I think you completely misunderstand what this bill represents. Read up on it www.patrick-breyer.de/en/posts/cha...
Chat Control: The EU's CSAM scanner proposal
🇫🇷 French: Traduction du dossier Chat Control 2.0, stopchatcontrol.fr🇸🇪 Swedish: Chat Control 2.0🇩🇰 Danish: chatcontrol.dk🇳🇱 Dutch: Chatcontrole
The End of the Privacy of Digital Cor...
www.patrick-breyer.de
October 7, 2025 at 8:15 AM
I think you completely misunderstand what this bill represents. Read up on it www.patrick-breyer.de/en/posts/cha...
Versioned deprecations: “Mark moved APIs with shims + deprecation notes.”
Use feature flags where risky: “Gate risky refactors behind flags if behavior might shift.”
Risk log: what could break, how we’ll detect it, and rollback plan.
Use feature flags where risky: “Gate risky refactors behind flags if behavior might shift.”
Risk log: what could break, how we’ll detect it, and rollback plan.
September 29, 2025 at 8:32 PM
Versioned deprecations: “Mark moved APIs with shims + deprecation notes.”
Use feature flags where risky: “Gate risky refactors behind flags if behavior might shift.”
Risk log: what could break, how we’ll detect it, and rollback plan.
Use feature flags where risky: “Gate risky refactors behind flags if behavior might shift.”
Risk log: what could break, how we’ll detect it, and rollback plan.
These could be useful too.
Preserve behavior: “No functional changes; if behavior must change, call it out explicitly.”
Small, reversible steps: “Propose a sequence of tiny PR-sized steps (each independently shippable).”
Tests stay green: “Surface any tests that will need updating and why.”
Preserve behavior: “No functional changes; if behavior must change, call it out explicitly.”
Small, reversible steps: “Propose a sequence of tiny PR-sized steps (each independently shippable).”
Tests stay green: “Surface any tests that will need updating and why.”
September 29, 2025 at 8:32 PM
These could be useful too.
Preserve behavior: “No functional changes; if behavior must change, call it out explicitly.”
Small, reversible steps: “Propose a sequence of tiny PR-sized steps (each independently shippable).”
Tests stay green: “Surface any tests that will need updating and why.”
Preserve behavior: “No functional changes; if behavior must change, call it out explicitly.”
Small, reversible steps: “Propose a sequence of tiny PR-sized steps (each independently shippable).”
Tests stay green: “Surface any tests that will need updating and why.”
It depends. But I'm closer to DevB. Improving soft skills is a harder job than improving technical ones. I think there is a certain threshold on the soft skills side that is a hard requirement, not an option. If DevA is passing that, then I can go with them too, depending on my needs in the team.
September 22, 2025 at 11:14 AM
It depends. But I'm closer to DevB. Improving soft skills is a harder job than improving technical ones. I think there is a certain threshold on the soft skills side that is a hard requirement, not an option. If DevA is passing that, then I can go with them too, depending on my needs in the team.