mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Serverstatistik:

1,4 Tsd.
aktive Profile

#developing

0 Beiträge0 Beteiligte0 Beiträge heute

alojapan.com/1272918/osaka-gas Osaka Gas lends hand in developing India’s gas lines #developing #gas #Hand #indias #lends #lines #Osaka #OsakaTopics #大阪 #大阪府 OSAKA — Japanese utility Osaka Gas will take part in developing India’s gas infrastructure through a partnership with a local supplier that has a significant reach in the promising market. A consortium led by Osaka Gas spent about $370 million in April to secure a 25% stake in Singaporean energy provider AG&P LN…

Technical Excellence: Lost. Like Atlantis. But with more AI JavaScript.

Once upon a time, engineers knew things. Not Googled things. Crafted things. We automated builds, wrote real tests, treated code like it could explode if mishandled, which it did, and we were proud when it didn't. It was elegant. Precise. Shameful if the customer found a bug. Now? It's fashionable to push broken features into production and call it MVP.

Nowadays, we want to engineer. But we don't get the space for applying our knowledge. Every training is useless when you can't apply it.

"Senior Developers" parade around with 10 years of experience by repeating the same year 10 times. They chant Clean Architecture but build everything in main(). They talk about TDD, then mock their way into oblivion. They don’t refactor, as it's not in the ticket. They don’t simplify, they just make it work. They wait for ticket assignments like robots awaiting firmware updates.
Worse: nobody creates anymore. They consume tools. No one understands the layers. No one asks why.

Agility? Without engineering excellence, it's just theatre. You can't move fast if you don't know how your engine works.

Want to be agile? Build engineers who:
* Understand architecture beyond drawing hexagons.
* Write tests that assert behaviour, not just lines executed.
* Know the cost of a dependency.
* Automate not for fun, but for resilience.
* Take responsibility before being told to.
* Stop chasing tools & Start understanding systems.
* Build things that work, not just compile.

Technical excellence is not a luxury. It's the foundation. And without it, you're not building software. You're just decorating the Titanic.

Agility without engineering is chaos in a hoodie.

Fortgeführter Thread

The biggest thing stopping the #mac from being a good source for #gaming is actually the difficulty it takes in developing games that can run on the mac and run well. #Apple likes to tote there capabilities,but what they don't say is that #developing for the mac takes twice as long as to develop the same for windows, not to mention that on an accessibility scale, it is not easy to use #XCode to directly code on the mac, trust me, I've tried and i found it way easier to use #VSCode to make even basic programs whereas for the mac, using XCode to do the exact same thing is like 10 times slower and harder to do for the same amount of work simply because of navigation alone with #VoiceOver.