We already know you’re a code connoisseur, but are you a word whiz? Check out how these devs are putting their Connect 8 skills to the test. Can you beat them? Show off your smarts in the comments!
Chrome for Developers’ Post
More Relevant Posts
-
Entropy has many enemies, but it's clearly the worst enemy of your code base. I like to add "entropy fighting" meetings in the dev lifecycle. Simple concept, you grab your whole team for an hour or two, you go over the PRs that went through during the current month, and you make sure to strengthen everything. - Are things properly named? - Are all features elegantly tied together? - Are all comments relevant, and are we missing some? - Should some things be abstracted? - Are there things we can do to improve the parallelization of work? - etc, etc, etc. It's been effective, it keeps everyone on the same page and ensures that code bases do not degenerate over time, even under tight pressure.
To view or add a comment, sign in
-
Good tips on this video... Regarding #5 though, I usually just go ahead and refactor the code without raising any backlog item. IMHO a good Senior Dev needs to be someone who is obsessed about code quality... someone who takes pride in his/her work and is willing to use it as a showcase on how things can get done. Code quality again in my opinion means code that is well commented and easy to figure out/understand. It can be copy pasted code instead of intricate code people in the team are afraid to update because it is difficult to understand.
How Senior Programmers ACTUALLY Write Code
https://www.youtube.com/
To view or add a comment, sign in
-
Hey Dev Gang! Guess what? My code just told me a joke! No kidding, it said, "Why do programmers prefer dark mode? Because light attracts bugs!" 😂 Life as a developer is like debugging a sitcom sometimes. Share your favourite code-related jokes below and let's turn this thread into a coding stand-up night! 💻 Remember, laughter is the best syntax error handler. Happy coding, and may your bugs be as easy to fix as typos! 🐞✨ #CodeHumor #DevLife #ProgrammingJokes #StandUpCoding
To view or add a comment, sign in
-
Navigating through the code after fixing a bug like a coding wizard, knowing very well it's just a temporary victory? We got your covered! 1. 🔍 Identify the bug like a detective. 2. 🤔 Scratch your head a bit; it's okay, bugs can be tricky! 3. 💻 Write some code. If it doesn't work, write more code. 4. 🧐 Stare at the screen, hoping for a magical solution. 5. 📚 Consult the documentation like it's the Bug Fixer's Bible. 6. 🤯 Experience a eureka moment that may or may not be real. 7. 🚧 Implement a fix. If it fails, pretend it's a feature. 8. 🔄 Repeat steps 3-7 until bug begs for mercy. 9. 🤞 Cross your fingers and pray to the coding gods. 10. 🚀 Deploy the "fix." Fingers crossed, again! #BugFixingAdventures #DeveloperLife #CodingJourney 🧙♂️🐛 #CoderLife #BugSquasher
To view or add a comment, sign in
-
Developers love to code, that's what we do. But, sometimes you need to take a step back and look at the bigger picture - and ask good questions such as: what problem are we solving, why are we doing this, etc. Questions are the answer, and they allow you to plan more effectively. Check out the top 3 tips for devs, from technical to non-technical: https://lnkd.in/gyzTDSrM
3 tips all Devs should know
https://www.youtube.com/
To view or add a comment, sign in
-
I draw pictures in my code sometimes. This may sound silly, but there's a lot of utility in it. Obviously this is less than ideal if you have a tight deadline, or if the code is simple and easy to navigate, but if you keep getting lost in your code or you have a LOT of repetitive code, this is a fast way to find your place and save tons of time when trying to find your place. #programmingtips #codingninjas #softwaredevelopment #workhacks
To view or add a comment, sign in
-
Do you know the difference between Constructive algorithm and Implementation problems in Codeforces? Well, Constructive algorithm problems require you to build or construct a solution from scratch based on given constraints. Your solution usually needs to be verified or proven correct, often through logical reasoning or validation. On the contrary, Implementation problems focus on coding up a given algorithm or performing specific operations based on the problem statement. The solution is relatively easy to come up with, but difficult to implement. In a humorous sense, we can say, " first one takes either 0 or 10 milion years to think and 0 second to code and the other one takes 0 seconds to think and 10 milion years to code". Do you have any thoughts on this?
To view or add a comment, sign in
-
|| Software Engineer |SDLC | C# | .Net | ASP .Net Core | JavaScript | WPF | WCF | SAP Crystal Reporting | MS SQL| Leadership | Angular || <Full Stack Developer>
Sure, he's paid to break your code! ◦ Me, watching code testers after I spend all night fixing bugs, Respect the hustle, my dudes, but maybe there's a less destructive way to find errors? Developers, this is what happens when you skip writing unit tests And remember, Auditing your own code is like grading your own homework, you're probably biased Let the professionals handle the stress tests, and focus on writing code that rocks, not crumbles. #testers #mycode #checking #fun #with #me. #but #happycoding
To view or add a comment, sign in
-
Decoding developer lingo: What developers say vs. what they mean! 🤓💻 Unravel the mysteries of code with a touch of humor. 😅 #DeveloperSpeak #CodeHumor #TechTalk #ProgrammingLife #DevHumor #DecodeTheCode #BehindTheScreens #GeekSpeak #TechJargon
To view or add a comment, sign in
-
🔥 Battling buggy code? It's time to crush and conquer for the might of clean code and readability in your projects. Chaotic code is a silent assassin, causing delays, frustration, and ultimately shackling your clan's productivity. Seize the power of clean code—forge alliances, enhance maintainability, and bid farewell to those pesky bugs. Unintentionally slowing down your tribe? Here's the remedy: 1. Meaningful Variable Names: 🕵️♂️ Don't make your comrades solve riddles. Choose names that weave a tale. 2. Consistent Formatting: 🧹 A tidy layout is a joy to work with. Consistency breeds understanding. 3. Strategic Nesting: 🏗️ Stack your code wisely. Each level of nesting should sharpen clarity, not breed chaos. Share your battle-tested tips for clean code below! #OrcDev #CleanCode #CodeMastery #DeveloperTribe #ReadabilityReigns
To view or add a comment, sign in
4,133 followers