Walt Disney Animation Studios’ Post

As a software engineer, I'd like to help other software engineers about software engineering so other software engineers can read the code because of another software engineer's poor hacky solutions that involved other software engineers not writing clean code leading new software engineers to scratch their head and blame other software engineers in the ability to software engineer. - Any large codebase. Real talk. I learned this a few years ago from an excellent mentor. We don't solve the problem with "Let's rewrite this". But rather, how can we find a solution to move forward and deprecate older parts. Tech debt is going to happen, but with a focused product, it can be cleaned up with new releases. Perfect code is no code. The most frustrating part is the question "Why would you write it this way...".

Working with more than 50 projects now, here are my top 10 pieces of advice for founders building MVPs 1) Customers are a waste of time. Don’t talk to them. 2) Keep changing the branding. Those colours really make a big difference 3) Hire a large team of software engineers. Use code. We need more engineers in the world 4) No need to spend time on marketing. Total waste! 5) Build it and they will come 6) Add more features to your MVP. Must have at least a dozen working links in the footer! 7) Dark mode is a must have 8) Your MVP must solve 3 problems for 3 different customers 9) When you hear feedback from prospective customers, ignore it completely. They don't really understand! 10) Don't follow zubair_nocode or his lovely tips about #nocode and #bubble

What inspired you to pursue a career in software engineering? Hi, I’m Ashan Beruwalage, a software engineer with 8+ years of experience in full stack development. I’m passionate about building scalable web and mobile applications, and optimizing for performance. My tech journey was motivated by my love for mobile game development. I enjoyed solving complex problems and turning ideas into interactive  experiences. This passion grew as I realized I could create solutions that help people in real life. I’d love to learn more about your journeys in tech! 💻 #SoftwareEngineering #TechJourney #CareerGrowth ________________________ 🤔 As a software engineer, have you ever wanted to write on LinkedIn but didn’t know where to start? Then "The 7 Days of LinkedIn Writing for Software Engineers" challenge is for you. 👉 Join the challenge. Link is in the comment section . #7DaysOfLinkedInWritingForSoftwareEngineers #day1

One little tip for junior developers and engineers looking to find their first job in the space: Personally if I don't see any well-put-together project made during nights and weekends that isn't a copy-paste of a YouTube video, it raises a red flag. Put in the effort to create something unique and show your passion. This will make you stand out and demonstrate your ability to think independently.

Creative Worker? Software Engineer? Doing Any Work That Requires Quite Some Focus and Thought Process? Ever Felt Keyboard ⌨️ Rut? Or something similar? 😮😲😯 What Do You Do In Such Situations? 🧐💭 I usually try to rest. What about You?

It's easy to be impressed when you hear about a company with a large team. But at RapidZapp we keep out team really lean. Why? We'd rather hire one senior, brillaint developer to build your prouduct over three junior devs who step on each other's toes and drag out a project. Hiring fewer higher caliber developers means that we avoid the miscommunication, confusion and disagreements that often comes from having several people work on the same code base. We find that less is more. Do you believe in smaller, tighter teams or go the more-is-merrier route?

Knowledge workers (and especially software developers) are living in a Kodak world. We are the film of old. Nothing wrong with that unless it's your identity. Case in point. I am not a software engineer. I conceptually understand service layers, dependency injection, separation of concerns, do not repeat yourself, and things like that. I can read code and have a solid idea about what it's doing. But I can't write it . . . until now. And I'm not really writing it. I'm telling my copilot what I want. Asking for code reviews and explanations. Making small changes, and so forth. Truly, this is amazing. It is far beyond moving from 35mm film to digital.

BLOGGED: The Problem with Most R&D Teams For many software developers, career success comes when they are placed on the "R&D" (research and development) team. It seems like a golden ticket kind of role: Spend time exploring new technology (which lots of developers enjoy doing), weighing in, offering insights, and just... it's like, all play, and no deadlines! And yet, strangely (or perhaps not), those teams never seem to last long--they go through one, maybe two iterations on something, and then the team is broken up and nothing replaces it for a few years until a new VP comes along and says, "Wait, who's tracking our future direction?" and forms one again.... Only to have it dismember again in a year or two. What gives? https://lnkd.in/g8jXpVBr

Anyone else riding the fine line between “Let’s do it” and “Please, for the love of code, No...”? Being a Principal Software Engineer is all about perfecting the art of saying yes while silently screaming no inside. My daily routine: ✅ YES, we can add another feature. Who needs sleep when you’ve got coffee, right? ❌ NO, we probably shouldn’t test that update directly in production. But hey, what could possibly go wrong? It’s a delicate balance between keeping the peace and avoiding catastrophic software meltdowns. I’m practically a professional juggler of features, deadlines, and the occasional bug that refuses to go away. From your friendly neighborhood Principal Software Engineer, who says “yes” just enough to keep things moving, and “no” just enough to keep it all from exploding. 💥 #yesmanvsnoman #principalengineerlife #codeandchaos #jugglingact #progressoverpanic

A software engineer is not a code writer ..