#readablecode — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #readablecode, aggregated by home.social.
-
https://www.europesays.com/ie/481605/ A Former OpenAI Employee Explains the ‘Open Secret’ of AI #AI #ArtificialIntelligence #ArtificialIntelligenceIndustry #ArtificialIntelligence #BusinessInsider #Company #DanielKokotajlo #Éire #Employee #ForecastingResearch #FormerOpenaiEmployee #FutureAiSystem #GoalHuman #HumanInstruction #IE #Ireland #MorePowerfulModel #Planning #ReadableCode #ReliableWay #researcher #Technology
-
🚀 Breaking news: Someone invented a #font for programmers who think more #symbols = more skills. Because clearly, what the world needs right now is a typeface that resembles an alien language 🤖. Who needs readable code when you can have hieroglyphics? 🙃
https://github.com/sayyadirfanali/Myna #programming #tech #news #alienlanguage #readablecode #hieroglyphics #HackerNews #ngated -
🚀 Breaking news: Someone invented a #font for programmers who think more #symbols = more skills. Because clearly, what the world needs right now is a typeface that resembles an alien language 🤖. Who needs readable code when you can have hieroglyphics? 🙃
https://github.com/sayyadirfanali/Myna #programming #tech #news #alienlanguage #readablecode #hieroglyphics #HackerNews #ngated -
🚀 Breaking news: Someone invented a #font for programmers who think more #symbols = more skills. Because clearly, what the world needs right now is a typeface that resembles an alien language 🤖. Who needs readable code when you can have hieroglyphics? 🙃
https://github.com/sayyadirfanali/Myna #programming #tech #news #alienlanguage #readablecode #hieroglyphics #HackerNews #ngated -
🚀 Breaking news: Someone invented a #font for programmers who think more #symbols = more skills. Because clearly, what the world needs right now is a typeface that resembles an alien language 🤖. Who needs readable code when you can have hieroglyphics? 🙃
https://github.com/sayyadirfanali/Myna #programming #tech #news #alienlanguage #readablecode #hieroglyphics #HackerNews #ngated -
"Code is like a story; make it readable, even beautiful." – Unknown
#CodeAsArt #ReadableCode -
"Code is like a story; make it readable, even beautiful." – Unknown
#CodeAsArt #ReadableCode -
💡 The best code?
Not the one that works — the one that’s understood.
📈 Maintainability. Scalability. Elegance.
🚀 *Level up your mindset — follow us for more wisdom.*
🌐 syngrid.com | ☎️ +65 6659 3971
#CodeQuote #DeveloperMindset #SyngridSolutions #TechExcellence #ReadableCode #DigitalArchitects #SimpleIsSmart #SoftwareWisdom #MotivationPoster #MondayMorivation #SyngridTechnology #Insipiration #singapore -
Why @Annotations Will Eventually Burn You.
Preach annotation voodoo or embrace explicit method calls? Too many still cling to @PreAuthorize, entrusting their fate to framework black magic. But such blind faith is brittle. One innocent Spring Boot update, and suddenly your security vanishes unless you summon an obscure @Enable... incantation.
Prefer the custom preauthorize() method: it’s concrete, predictable, and the compiler screams when something breaks as it should. Just like how constructor injection finally defeated the field-injection cult, it’s time to retire annotation worship elsewhere too.
Consider @JsonProperty("fieldName"): sure, the object mapper might infer names correctly without it, until one day it doesn’t, because the naming strategy changes behind your back. It’s happened. It will happen again. That’s the price of depending on invisible magic. Unreadable, unpredictable, unmaintainable. Same applies to reflection.
Frameworks and their “best practices” are relics of the monolith age. Java has evolved: threads, HTTP services, logging,… all can now be built functionally, fluently, and natively. It’s not Java vs Kotlin or some trendy syntax candy. Languages, especially those that compile, already give you more than enough. The bottleneck isn’t the tool, it’s the one holding it.
#Java #SpringBoot #CleanCode #SoftwareEngineering #CodeQuality #Programming #ModernJava #DeveloperExperience #DevMindset #NoMoreMagic #ReadableCode #ExplicitOverImplicit #SayNoToAnnotations #SeparationOfConcerns #FunctionalProgramming
-
Why @Annotations Will Eventually Burn You.
Preach annotation voodoo or embrace explicit method calls? Too many still cling to @PreAuthorize, entrusting their fate to framework black magic. But such blind faith is brittle. One innocent Spring Boot update, and suddenly your security vanishes unless you summon an obscure @Enable... incantation.
Prefer the custom preauthorize() method: it’s concrete, predictable, and the compiler screams when something breaks as it should. Just like how constructor injection finally defeated the field-injection cult, it’s time to retire annotation worship elsewhere too.
Consider @JsonProperty("fieldName"): sure, the object mapper might infer names correctly without it, until one day it doesn’t, because the naming strategy changes behind your back. It’s happened. It will happen again. That’s the price of depending on invisible magic. Unreadable, unpredictable, unmaintainable. Same applies to reflection.
Frameworks and their “best practices” are relics of the monolith age. Java has evolved: threads, HTTP services, logging,… all can now be built functionally, fluently, and natively. It’s not Java vs Kotlin or some trendy syntax candy. Languages, especially those that compile, already give you more than enough. The bottleneck isn’t the tool, it’s the one holding it.
#Java #SpringBoot #CleanCode #SoftwareEngineering #CodeQuality #Programming #ModernJava #DeveloperExperience #DevMindset #NoMoreMagic #ReadableCode #ExplicitOverImplicit #SayNoToAnnotations #SeparationOfConcerns #FunctionalProgramming
-
Why @Annotations Will Eventually Burn You.
Preach annotation voodoo or embrace explicit method calls? Too many still cling to @PreAuthorize, entrusting their fate to framework black magic. But such blind faith is brittle. One innocent Spring Boot update, and suddenly your security vanishes unless you summon an obscure @Enable... incantation.
Prefer the custom preauthorize() method: it’s concrete, predictable, and the compiler screams when something breaks as it should. Just like how constructor injection finally defeated the field-injection cult, it’s time to retire annotation worship elsewhere too.
Consider @JsonProperty("fieldName"): sure, the object mapper might infer names correctly without it, until one day it doesn’t, because the naming strategy changes behind your back. It’s happened. It will happen again. That’s the price of depending on invisible magic. Unreadable, unpredictable, unmaintainable. Same applies to reflection.
Frameworks and their “best practices” are relics of the monolith age. Java has evolved: threads, HTTP services, logging,… all can now be built functionally, fluently, and natively. It’s not Java vs Kotlin or some trendy syntax candy. Languages, especially those that compile, already give you more than enough. The bottleneck isn’t the tool, it’s the one holding it.
#Java #SpringBoot #CleanCode #SoftwareEngineering #CodeQuality #Programming #ModernJava #DeveloperExperience #DevMindset #NoMoreMagic #ReadableCode #ExplicitOverImplicit #SayNoToAnnotations #SeparationOfConcerns #FunctionalProgramming
-
Why @Annotations Will Eventually Burn You.
Preach annotation voodoo or embrace explicit method calls? Too many still cling to @PreAuthorize, entrusting their fate to framework black magic. But such blind faith is brittle. One innocent Spring Boot update, and suddenly your security vanishes unless you summon an obscure @Enable... incantation.
Prefer the custom preauthorize() method: it’s concrete, predictable, and the compiler screams when something breaks as it should. Just like how constructor injection finally defeated the field-injection cult, it’s time to retire annotation worship elsewhere too.
Consider @JsonProperty("fieldName"): sure, the object mapper might infer names correctly without it, until one day it doesn’t, because the naming strategy changes behind your back. It’s happened. It will happen again. That’s the price of depending on invisible magic. Unreadable, unpredictable, unmaintainable. Same applies to reflection.
Frameworks and their “best practices” are relics of the monolith age. Java has evolved: threads, HTTP services, logging,… all can now be built functionally, fluently, and natively. It’s not Java vs Kotlin or some trendy syntax candy. Languages, especially those that compile, already give you more than enough. The bottleneck isn’t the tool, it’s the one holding it.
#Java #SpringBoot #CleanCode #SoftwareEngineering #CodeQuality #Programming #ModernJava #DeveloperExperience #DevMindset #NoMoreMagic #ReadableCode #ExplicitOverImplicit #SayNoToAnnotations #SeparationOfConcerns #FunctionalProgramming
-
Why @Annotations Will Eventually Burn You.
Preach annotation voodoo or embrace explicit method calls? Too many still cling to @PreAuthorize, entrusting their fate to framework black magic. But such blind faith is brittle. One innocent Spring Boot update, and suddenly your security vanishes unless you summon an obscure @Enable... incantation.
Prefer the custom preauthorize() method: it’s concrete, predictable, and the compiler screams when something breaks as it should. Just like how constructor injection finally defeated the field-injection cult, it’s time to retire annotation worship elsewhere too.
Consider @JsonProperty("fieldName"): sure, the object mapper might infer names correctly without it, until one day it doesn’t, because the naming strategy changes behind your back. It’s happened. It will happen again. That’s the price of depending on invisible magic. Unreadable, unpredictable, unmaintainable. Same applies to reflection.
Frameworks and their “best practices” are relics of the monolith age. Java has evolved: threads, HTTP services, logging,… all can now be built functionally, fluently, and natively. It’s not Java vs Kotlin or some trendy syntax candy. Languages, especially those that compile, already give you more than enough. The bottleneck isn’t the tool, it’s the one holding it.
#Java #SpringBoot #CleanCode #SoftwareEngineering #CodeQuality #Programming #ModernJava #DeveloperExperience #DevMindset #NoMoreMagic #ReadableCode #ExplicitOverImplicit #SayNoToAnnotations #SeparationOfConcerns #FunctionalProgramming
-
Code readability is important because it improves maintainability, promotes collaboration, reduces errors, and leads to robust, long-lasting codebases. Well-written code should strive to be self-explanatory through clear naming, structure, and idiomatic practices, with comments used sparingly to increase understanding (i.e. adding context that is not immediately obvious from the code itself), rather than to compensate for poor design.
I equate readability of code with beautiful code which can be efficient or optimized or both.
#BeautifulCode #ReadableCode #Programming #Code #Haskell #Python
-
Code readability is important because it improves maintainability, promotes collaboration, reduces errors, and leads to robust, long-lasting codebases. Well-written code should strive to be self-explanatory through clear naming, structure, and idiomatic practices, with comments used sparingly to increase understanding (i.e. adding context that is not immediately obvious from the code itself), rather than to compensate for poor design.
I equate readability of code with beautiful code which can be efficient or optimized or both.
#BeautifulCode #ReadableCode #Programming #Code #Haskell #Python
-
Code readability is important because it improves maintainability, promotes collaboration, reduces errors, and leads to robust, long-lasting codebases. Well-written code should strive to be self-explanatory through clear naming, structure, and idiomatic practices, with comments used sparingly to increase understanding (i.e. adding context that is not immediately obvious from the code itself), rather than to compensate for poor design.
I equate readability of code with beautiful code which can be efficient or optimized or both.
#BeautifulCode #ReadableCode #Programming #Code #Haskell #Python
-
Code readability is important because it improves maintainability, promotes collaboration, reduces errors, and leads to robust, long-lasting codebases. Well-written code should strive to be self-explanatory through clear naming, structure, and idiomatic practices, with comments used sparingly to increase understanding (i.e. adding context that is not immediately obvious from the code itself), rather than to compensate for poor design.
I equate readability of code with beautiful code which can be efficient or optimized or both.
#BeautifulCode #ReadableCode #Programming #Code #Haskell #Python
-
Code readability is important because it improves maintainability, promotes collaboration, reduces errors, and leads to robust, long-lasting codebases. Well-written code should strive to be self-explanatory through clear naming, structure, and idiomatic practices, with comments used sparingly to increase understanding (i.e. adding context that is not immediately obvious from the code itself), rather than to compensate for poor design.
I equate readability of code with beautiful code which can be efficient or optimized or both.
#BeautifulCode #ReadableCode #Programming #Code #Haskell #Python
-
"Programs must be written for people to read, and only incidentally for machines to execute." – Harold Abelson
#ReadableCode #ProgrammingWisdom -
"Programs must be written for people to read, and only incidentally for machines to execute." – Harold Abelson
#ReadableCode #ProgrammingWisdom -
Actually sidestepping the "comments bad" debate, if you can't read your code two weeks later, you have bigger problems. #readablecode
QT: https://social.cybre.town/@DeveloperMemes/107190603989169170 -
Actually sidestepping the "comments bad" debate, if you can't read your code two weeks later, you have bigger problems. #readablecode
QT: https://social.cybre.town/@DeveloperMemes/107190603989169170