Konrad Winnicki on LinkedIn: One of my job interviews was with the team using the Trunk-Based… (2024)

A junior dev and a senior dev read the same forum post on stack overflow.The code snippet there shows XYZ.What the junior will often write in their code: XYZ.What the senior will often write: 20% of XYZ+ 80% of A/B/C from other projects and custom code.Experience matters.#work #experience #developers #thoughts #forum

2

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.

2

I strongly prefer writing code that is simple to understand rather than refactoring with an advanced approach. 🧐In the real world, there's a high chance someone with minimal experience might take over your project.The key point is "Ensure that your code is always maintainable and scalable by adopting a simple approach."#softwaredeveloper #seniordeveloper #softwaredevelopment

4

Hi all!Today I'm gonna share with you a software development good practice to improve your #code Let's start! #CodeTip1.- YAGNI Principle.YAGNI stands for "You Ain't Gonna Need it", this principle tells us that you should only write the code that you need now.Don't write code that you don't need right now but you think you might need it in the future because that future may never come or the project requirements could change and you'll only waste your time and overcomplicate the project for other developers too.Remember you should write the minimum code needed to fulfill the project's requirements.This is all for today Folks! If you like it, remember to follow me and share it to spread the knowledge.See you on the next tip about #code #SoftwareDevelopment #goodPractices #SmartContracts #web3 #security

3

You're doing code review and want to 𝗶𝗿𝗿𝗶𝘁𝗮𝘁𝗲 𝘆𝗼𝘂𝗿 𝘁𝗲𝗮𝗺𝗺𝗮𝘁𝗲𝘀?Here's a cheat sheet 👇1. Never (ever) write useful advice 2. Leave short, indecipherable messages and expect people to understand what you're referring to 3. Get angry when people complain about your code review skillsWe all know that guy, right?#howNOTtoreviewcode #codereview #softwaredevelopment----------I'm Cristian Sarghe and I'm sharing slices of my 7+ years of Software Development experience - wins and losses, good decisions and mistakes.𝗖𝗼𝗻𝗻𝗲𝗰𝘁 or 𝗙𝗼𝗹𝗹𝗼𝘄 me to learn from my experience and become a better developer than I am!

4

Every developer should write code in a neat and clean manner so that it's easy for the next developers to understand. Also, every developer should make sure to follow best practices and at least have code review sessions.#CleanCodeForDevelopers #BestPractices #CodeReviewSessions

11

"Low Code vs. No Code: Demystifying the Landscape!" 🤔💻 Explore the nuances between these powerful development approaches. While Low Code offers flexibility, No Code simplifies without coding skills. Dive into the contrasts and find your perfect fit! 🌐🔍 ...#lowcode #lowcodedevelopment #lowcodenocode #nocode #nocodedevelopment #nocodeplatform #lowcodeplatform #techcomparison #lowcodedeveloper #nocodedeveloper #developer

2

When developers look at old code, it's like revisiting their past coding mistakes. 😂😂 In search of developers for your project? Explore our service 👉 https://lnkd.in/dV5rJ9mm.#invozone #readingoldcode #oldcode #developer #softwaredevelopers #softwaredevelopment

74

12 Comments

🚀 Developers, Please take care of your commit messages!Commits are quite important when it comes to a developers craft. They act as the icing on the cake of the code written, and when written correctly, they bring a huge amount of value. Not only to yourself, but also to your team members! A well-composed commit message is invaluable as it offers essential context to what has been worked on!👍 𝐆𝐨𝐨𝐝 𝐂𝐨𝐦𝐦𝐢𝐭 𝐌𝐞𝐬𝐬𝐚𝐠𝐞𝐬:✅ "feat: Add user authentication feature"✅ "fix: Resolve UI alignment issue on homepage"✅ "docs: Update README with installation instructions"✅ "refactor: Simplify data validation logic"👎 𝐁𝐚𝐝 𝐂𝐨𝐦𝐦𝐢𝐭 𝐌𝐞𝐬𝐬𝐚𝐠𝐞𝐬:❌ "Updated files"❌ "Bug fixes"❌ "Changes"❌ "More work"#developer #development #codingtips #git #programming #softwareengineering #softwaredevelopment

5

1 Comment

I listened to Travis' video about the 5 signs of an inexperienced self-taught developer. It aligns with what I'm learning from Dr. Emily in The Joy of Coding.Outlining key points to avoid on the path to becoming a quality developer, here are the signs:1. Only trying to make code work, and not going beyond to readability, maintainability, and scalability of your code.2. Make huge changes at once- pull requests are too big for any meaningful comments or remediation. Problems are harder to diagnose.3. Always learning new programming languages or frameworks instead of digging deep and mastering main concepts.4. Working on too many different things at once, thereby giving excuses for projects instead of delivering consistently on assignments. 5. Don't want others seeing or critiquing their code, because then they'd have to make changes and improve it instead of moving on.A more experienced dev takes the time to do things thoroughly and correctly, in a methodical and organized way, having integrity for the assignments they have committed to and accepts accountability from other team members. I see some soft skills here that can transfer from other work and life experiences, and it makes me excited to continue on in my journey because I know I'm on the right track!https://lnkd.in/gF9DBrxs

2