#readablecode 검색 결과

Consistent naming conventions prevent confusion and speed up collaboration. Never underestimate good naming. #CodingStandards #ReadableCode #DevBestPractices #SoftwareTips

Descriptive names for variables and functions prevent confusion and make code easier to maintain. #ReadableCode #CleanCode #DevBestPractices #SoftwareTips

Write code as if the next person to read it knows nothing. Clear names and comments prevent misunderstandings. #ReadableCode #CleanCode #DevBestPractices #SoftwareTips

If someone can’t tell what your PR does by reading the title and first few lines, rewrite it. Clarity scales. #ReadableCode #PRTips

Code is not self-explanatory. That’s a myth. Be kind. Write comments, name things well, and explain edge cases in PRs. #ReadableCode #DevMindset

You don’t need a PhD in compilers to ask for better variable names. Clarity is everyone’s job. #ReadableCode #DevTips

You don’t win points for clever code in a PR. You win trust for code others can read, reason about, and maintain. #ReadableCode #EngineeringWisdom

Messy code slows everything down. At CN Tech, we keep things clean, organized, and testable — so your project runs smoother and scales easier. #CleanCode #NoSpaghettiCode #ReadableCode #TestableCode #CNTech #SoftwareDevelopment

Think of clean code as a set of friendly rules that help everyone—your future self included—understand and work with your code. #CodeQuality #ReadableCode #MaintainableCode #Refactoring #SoftwareCraftsmanship #ProgrammingBestPractices #DevCommunity #CleanArchitecture

Writing comments? Good. ✅✅ Needing comments to explain your code? Bad. ❌❌ Code should read like a story, not a ransom note. 📖 #ReadableCode

@jeremybytes presents 'Code is for Humans' July 24th at Nebraska.Code(). nebraskacode.amegala.com #Code #ReadableCode #PracticalTechniques #IT #Nebraska #CleverCode #TechConference @teledigm @TabithaHealth @ChamberAurora @dopsoftware @TDatCCC @MidwestConnects @cccnebedu @obsoft

@jeremybytes presents 'Code is for Humans' July 24th at Nebraska.Code(). nebraskacode.amegala.com #Code #ReadableCode #PracticalTechniques #IT #Nebraska #CleverCode #TechologyConference @wewritecode @Tabs3Software @SDS2_Software @WesternBlotting @Vosaic @GetScoreVision @wabtec

📘 技術書紹介：『リーダブルコード』 定番だけど、今読んでも気づきがある。 「美しいコードは、他人の時間を尊重する」 チーム開発を学ぶ人ほど、読む価値あり。 #ReadableCode #CodingBestPractices #DevLife oreilly.co.jp/books/97848731…

Write code your teammates can understand. #ReadableCode #CleanCode #TeamCoding

🧑‍💻 “Code is for humans first, machines second.” – Harold Abelson Writing readable code isn't just smart — it's essential. 💬 Tag a dev who writes code like poetry 👇 #Scriptzol #CleanCodeMatters #ReadableCode #DeveloperWisdom #TechInspiration #HaroldAbelsonQuote #CodeForHumans

👥 Don’t force readers to hold logic in their heads. Flatten your code. Extract logic. Give your if conditions meaningful names like isValidUser(). Your code should read like a story, not a puzzle. #ReadableCode #Refactoring

Clarity in code is key; without it, even the best can get lost. Write as if explaining magic to a unicorn! 🦄✨ #ReadableCode #CodeWisdom

Pattern Matching Works Hand-in-Hand 🔥 With ADTs, pattern matching makes handling different cases intuitive and elegant, reducing the need for messy conditional logic. #PatternMatching #ReadableCode

12/16 ...with this clearer version: "if Passenger.FrequentFlierCategory in ([FrequentFlierCategories.Gold, FrequentFlierCategories.Diamond] & Flight.FirstClassAvailable()){ Flight.Upgrade(Passenger)}" #ReadableCode

💡 Escreva para humanos, não para máquinas. #BoaSemana #ReadableCode #CleanCode #Desenvolvimento #beecrowd 💡 Write for humans, not machines. #GoodWeek #CleanCode #Development #beecrowd 💡 Escribe para humanos, no para máquinas. #BuenaSemana #CleanCode #Desarrollo #beecrowd

Refactoring 15: Handling our inputs better We're taking in some data, and we're handling some exceptions. now let's go one stage further, and tidy up our input a little more. let's make it a class #ReadableCode

Refactoring 19: Using Our Framework Working with our client, we aid them to make use of the Laravel Setup to do some of this work, now we understand what is happening. Here's our controller after helping them do that: #ReadableCode

Refactoring 8: Exceptions At the moment we're echoing - but this isn't actually doing anything in our current process, as it just outputs the error to nowhere. note: die is a temporary measure as the current flow doesn't allow strong management yet #ReadableCode

Refactoring: Well there we have it, a whistlestop tour of refactoring unreadable code into more readable code. Does that mean this is now perfect? no not at all - but we've got a lot better than we did. It's now a lot more readable. #ReadableCode

Refactoring 2: Helpful Naming Of Variables Some of these variables can be easily identified by their use case - so let's create a bit of extra help by naming them a little better - again, helping the readability of the code. #ReadableCode

Refactoring 3: Our First Bug There's two queries at the bottom, but only one was being used. For the sake of argument, let's assume that a discussion was had with the customer, and the code should be doing both queries. #ReadableCode

Refactoring 5: A New Class So now we've separated things up, we can see a clearly useful class: one that handles the Query. We're not going to change any logic, just encapsulate it and make it more readable again. #ReadableCode

Refactoring 6: identifying another bug Whilst moving this to class, we noticed that the system is using the outdated mysqli service. Let's refactor this to be PDO, which is some what more secure, and also allows a clearer setup #ReadableCode

Refactoring 9: The Web Query As you can see, there's nothing protecting against the web query being what we expect - and we don't even know what it should be. A conversation with our client tells us it should be name and email address. #ReadableCode

Refactoring 10: examining the bf function so this function does a lot of stuff - but what does it actually do? at this point we break it down to find out what the code is doing. Let's insert some comments on it to help us out, based on the usage #ReadableCode

Refactoring 14: Sort Helper After talking to our customer, we discover that this is used all over the place - so let's make a sorting helper class, and also optimise the sort format. It's always 100% of the time integers in this use case. #ReadableCode

Refactoring 4: Re-ordering code Let's re-order things a bit - and get some more clarity on what's related to what. 1) a database connection 2) a set of data coming from the web GET request, and a query 3) a couple of functions, and a query #ReadableCode

Refactoring 7: More Control over our database We're currently passing in our query directly. There's nothing actually stopping that query being misused. We want to protect against injection even more, so let's create a few helper functions. #ReadableCode

Refactoring 11: Fixing the function a conversation with our client says this should be building an array of random numbers - they are generating a million so that there is enough to use for any use case, but this was broken. they also need 100 in this use #ReadableCode

Refactoring 13: Making Our Function More Readable Before going to our customer, we make this function infinitely more readable by using sensible naming functions and removing the second redundant sort, This makes it easier for our customer to understand. #ReadableCode

Refactoring 16: Extracting the Validator So now let's get another new class out of here - the Validator. We can build up a useable validator class quite easily that helps us to validate anything anywhere. Our client tells us this happens in lots of places. #ReadableCode

Refactoring 18: An Aside A Small aside on our refactoring - for simplicity, i have been including the code in one file - it's worth noting that these would be stored in separate files, and separate namespaces. It separates concerns, and helps readability #ReadableCode

Refactoring 12: Examining our second function we use the same process as before - adding comments to examine what is happening in our function, and then in the use case. we discover this is a sort algorithm, and can probably optimise, but we need the use case #ReadableCode

just dropped a book on code bookkeeping bc im tired of seeing y'all's spaghetti code 🍝 stop writing leetcode-style garbage that no one can read in 6 months. #SpaghettiCode #CleanCode #ReadableCode #CodeQuality #SoftwareDevelopment #ProgrammingTips #TechBooks

Refactoring 1: Simple Layout Changes We're going to start simply by putting in some whitespace to separate things up a bit - a wall of text is super-hard to read, so getting some spacing in there immediately helps us to understand what's happening a bit more. #ReadableCode