Daniel ‎דניאל

@kristijan_kralj IOC, reflection, all bullshit

The hidden cost of "enterprise" .NET architecture: Debugging hell. I've spent 13+ years in .NET codebases, and I keep seeing the same pattern: Teams add layers upon layers, to solve the problems they don't have. IUserService calls IUserRepository. IUserRepository wraps IUserDataAccess. IUserDataAccess calls IUserQueryBuilder. IUserQueryBuilder finally hits the database. I've seen a lot of classes having one-line methods whose sole purpose was to call the next layer and that's it. But to change one validation rule, you step through 5 layers. To fix a bug, you open 7 files. The justification is always the same: "What if we need to swap out Entity Framework?" "What if we switch databases?" "What if we need multiple implementations?" What if this, what if that. The reality: Those "what ifs" don't come to life in 99% of cases. I haven't worked on a project where we had to swap the ORM. But I've seen dozens of developers waste hours navigating through abstraction mazes. This happens with both new and experienced developers. New developers asking on Slack all the time: "Where to put this new piece of code?" But senior developers are too busy to answer that message. Why? Because they are debugging through the code that has more layers than a wedding cake. The end result? You spend more time navigating than building. Good abstractions hide complexity. Bad abstractions ARE the complexity. And most enterprise .NET apps? Way too much of the second kind.

@TerribleMaps Portugal the fruit

Countries where oranges are called “Portugal”

Sting talking about the evolution of listening music, from vinyls to streaming platforms.

@BallerToy1327 Still have them.

How many #Gobots did you have guys? Or did you tell your mom to buy me a #Transformers and you ended up with a much lower priced Leader 1 and not Optimus Prime?

@ShitpostGate Okaerinasai

@nedoliveira1 42 Agora vamos à pergunta.

Qual é a resposta para a vida, o universo e tudo mais?

@NodeChuck @TheDefiantGhost Sassaman

@TheDefiantGhost Adam Back was the crypto math guy, the engine builder. Nick Szabo was the idea guy, the architect. Hal Finney was the software engineer, the implementer, the debugger. McAfee is basically saying it was Back. But even with the British writing, the paper was most likely Szabo.

John McAfee on Satoshi Nakamoto's identity: "Let me give you some clues." "In Satoshi's white paper, every word that has dual spellings for American and British English is British. It is all British." "Every sentence is followed by two spaces. Now that's a minority choice in most, but two spaces." "There are only two that can be accused who were British, and only one of those has two spaces in every one of his papers." "Figure it out, people. It'll take you 15 minutes."

@ChosenAutocrat @TheDefiantGhost Yesss

@TheDefiantGhost His name was Len Sassaman

@TheDefiantGhost Sassaman

@ClassicGIJoe It was epic

The GI Joe Killer W.H.A.L.E. Hovercraft from 1984. It had so much playability - depth charges, a motorbike, twin fans, missiles, 2 gun turrets, a hold and a recon sled. It even floated! Who had it? Was this the great Joe vehicle ever?

@kaaaash____ Neither. Logitech Anywhere 2S

Be honest, Left or Right

@bestofStarTrek Why not both?

Sisko or Janeway?

@ComuDoMega E quake 3? Doom 3? Cada um teve sua evolução tecnológica

A Id Software revolucionou o gênero FPS, pelo menos, três vezes. A 1ª com Wolfenstein 3D. A segunda vez com DOOM, ao ponto que durante quase uma década todo jogo de FPS era referido como tipo DOOM. E uma terceira vez quando introduziram Quake como o 1º jogo FPS totalmente poligonal. Quem aqui jogou Quake naquele Pentium 100 mhz?

@urubullish 99% é o estado

90% dos problemas é a gente mesmo que cria…. os outros 10% é o estado! Larga tudo e vai viver!

@cinecitta2030 Where’s the potato salad?

Wake up babe you were dreaming about the giant Wiener Schnitzels again

@bestofStarTrek Why not both?

Deep Space Nine or Next Generation?

@TheDataHubX Where’s Portugal ffs

Top 20 Oldest Countries in the World 1. 🇮🇷 Iran ~4600 years 2. 🇮🇳 India ~4500 years 3. 🇨🇳 China ~3600 years 4. 🇹🇼 Taiwan ~3600 years 5. 🇦🇹 Austria ~870 years 6. 🇮🇹 Italy ~300 years 7. 🇦🇫 Afghanistan ~278 years 8. 🇰🇼 Kuwait ~273 years 9. 🇶🇦 Qatar ~147 years 10. 🇬🇷 Greece ~204 years 11. 🇨🇱 Chile ~215 years 12. 🇻🇪 Venezuela ~215 years 13. 🇨🇴 Colombia ~215 years 14. 🇲🇽 Mexico ~215 years 15. 🇦🇷 Argentina ~215 years 16. 🇧🇷 Brazil ~203 years 17. 🇺🇾 Uruguay ~200 years 18. 🇧🇴 Bolivia ~200 years 19. 🇳🇿 New Zealand ~172 years 20. 🇷🇴 Romania ~166 years Note: Values are approximate and based on historical sovereignty timelines. Exact figures may vary due to different interpretations. Source: World Population Review

@gersongomes E se errarem um pouco e escaparem da gravidade da lua?

Haja cálculos matemáticos! 😳 Esta animação, incluindo o deslocamento da lua, nos mostra a complexidade da missão.

@hoje_no Enquanto eles puderem executar esse pedagio…

O plano do Irã é classificar as nações do mundo em 3 categorias: hostis, neutros e amigos. Os hostis (EUA, Israel) serão banidos de passar pelo Estreito de Ormuz, os neutros (países europeus e alguns asiáticos) deverão pagar pedágio e os amigos (provavelmente Índia, China, Rússia, África do Sul, Brasil (??) e mais alguns poucos) poderão passar livremente.