8 Career Tips from My 25 Years as Developer

[@TheSuikoEnjoyer]

The thing you need to remember the most is not to stress out over work, don't get anxious, paranoid or go parabolic if something goes wrong or starts bursting into flames, especially if it's not your fault. Keep in mind that your health is more important than any company you work for, you are replaceable to them, your health isn't replaceable to you.

[@acavbeats]

Great point

[@LaravelDaily]

Very important, agreed.

[@rajaasyraf25]

I do get anxious sometimes, but not because something goes wrong and didn't go as planned, but I get anxious thinking at any time my boss will scold me in front of others and never want to listen to my explanation. Any advise how to manage this?

[@TheSuikoEnjoyer]

@rajaasyraf25 That has never happened to me before. Maybe I just had luck with the companies I worked at? Could also be the way you handle yourself from the very beginning when it comes to communication in general.

[@heitorasf]

​@@rajaasyraf25if u can report to HR or look for another job.

[@luishamedmedinavaca377]

Third advice is so important. I have struggled too much in the past just because i underestimated the work.

[@JJJMMM1]

My #1 tip for new developers: figure out what the client _actually_ needs, not what they _say_ they need. The people you interact with are not usually professionals developers. It's your job to dig deep until you discover what the software needs to achieve. Get to know the problem domain. And when you make your design proposal, mercilessly cut out all extraneous features, and justify every decision. If you're right, it's hard for them to disagree.

[@LaravelDaily]

Very good point!

[@CHSKnight]

Thank you sir. I am enjoying Laravel more because of your content and tutorials

[@techjitendranadol9876]

Sir, your ideas and tips made my career much forward

[@yvesengt]

I like your new car! 🤣 Thanks for those videos! Very insipiring and useful

[@LoganathanNatarajanlogudotcom]

Thank you. really it will help people to realize and improve their career ...

[@md.raysulkobir6303]

Thank you sir.

[@richardwheatley7194]

Worth noting that if you are working for free you are effectively getting your paying clients to subsidise your non paying clients.

[@ЖеняХристенко-е3ы]

Thanks for the tips ! It is inspiring!

[@leonardorochalino]

nice job,i like laravel for your influence!

[@PrajwalMaharjan-bc1sp]

Hey, could you create a video explaining Laravel Octane? I'd love to see an overview of its benefits (like performance improvements) and downsides (such as memory leaks or state persistence between requests). It would be really helpful if you could cover best practices for using Octane properly, how to manage state correctly, and how to avoid common pitfalls.

[@LaravelDaily]

I don't have enough practical experience with it, unfortunately, never really needed it. But here's a great article: www.galahadsixteen.com/blog/from-zero-to-35m-the-struggles-of-scaling-laravel-with-octane

[@Hman165]

One i learned the hard way : Don't stay in a place where you don't learn anything

[@markos8971]

Pavilas thank you for sharing your wisdom. I've progressed so much by following you and watching tips you share. You have inspired many of us. I would like to hear your thoughts on "over delivering" features on the project then initially agreed. It makes clients happy, at least in my case. I think I am as well pushing myself to explore more than just satisfying "requirement". Your thoughts on this?

[@LaravelDaily]

It depends on the situation and what benefit you or company have from overdelivering. Some clients don't appreciate it enough and you'd rather spend your energy elsewhere.

[@rogerflatt8054]

I'll add my 40+ years experience as a (mostly freelance) software developer/designer (London/UK/NL/US) and agree with EVERY. SINGLE. WORD. OF. THIS. BONUS TIP #9: Learn diplomatic ways to say "No! F*** off!" - Perhaps something like : "No, no, no, that's not possible with current scheduling, deadlines and limited dev/test/devops resource. NOT. CURRENTLY. POSSIBLE." [[ Be very wary of flexible requirements with *in*flexible delivery dates ... every change is a renegotiation. Get it in writing. See point #9 above. ]] [[ And watch out for that favourite trick of Project Managers - add a new 5-day dev feature, and reduce the testing phase by 5-days ... #HowToKillAProject. How we laughed as everything burst into flames on release ...

[@LaravelDaily]

Thanks, very valuable comment!

[@rogerflatt8054]

@@LaravelDaily 😁😂 #TrueStory

[@MuhdBasiirZulkifle]

1. Make your skills visible by engaging in communities and networking - invisibility reduces opportunitiess 2. Learn from developers using different technologies to gain diverse perspectives and reduce framework biass 3. Take time to properly estimate work instead of giving immediate optimistic timeliness 4. View large backlogs as job security rather than complaining about workloads 5. Develop strong negotiation skills to handle situations where management makes promises without developer consultations 6. Focus on project delivery when dealing with difficult team members while maintaining professional relationshipss 7. Master your development tools and shortcuts to optimize workflow efficiencys 8. Stay curious and adaptable, especially with emerging technologies like AI, to maintain career relevances

[@X-factor6]

Your success = your skills + how many people know about them

[@zxyi9090]

Let your work speaks for you. Be vigilant.

[@LaravelDaily]

Partially disagree, because for developers the work is not often that visible by itself, unless you or someone else SHOWS the work and talks about it to someone

[@zxyi9090]

@LaravelDaily you have a point. I once said your value as a software developer and your reputation is made when you leave to another company. I believe that anyone can write code that machines understand. However we write code to extend and be easily modified through extension. In my life I have seen lots of code abuse not even the original developer knows what it does. When you write clean modular code indirectly you are making up your reputation for those who cares.

[@ramina2121]

Do not be oriented to money only. You may start good salary job in a company but could not increase or experience and get new knowledge. and stayinging in that company for money will hit you later when you try to change the job but every are ahead of you. Because they may worked on lower salary but increased as developers and now they have the opportunity.

[@LaravelDaily]

Very good point!

[@noushedakib1658]

Thank You

[@lycan3868]

thank you for all the tips, but if you don't mind i have two questions, first one is: is it ok to use chatgpt cuz some people told me it's gonna make you lazy and affect my learning process, and second question is: is it ok to jump from a programming language to another cuz i've worked with 4 different companies and in each company i had to work with a different programming language either for backend or frontend i even had some devops task

[@LaravelDaily]

I think both topics deserve a video from my office, with a longer answer. So, subscribe to the channel and you'll be answered :)

[@LaravelDaily]

The answer published in this video: kzbin.info/www/bejne/rKvShYinityqqMU

[@lycan3868]

@@LaravelDaily thank you so much

[@jayadevrath2364]

Thanks 🙏🙏

[@X-factor6]

Nice advices

[@iconicae8814]

I don't understand why companies ask for php doctrine with laravel on linkdin and some companies asks for Kafka , Redis and Docker in backend roles , isn't That devoops responsibilities?

[@LaravelDaily]

If those companies have DevOps, then it's their responsibilities. Not every company can afford to have separate DevOps.

[@iconicae8814]

@@LaravelDaily Got it

[@DominiK037]

Networking yup

[@JustinGiglio-o3f]

cool

[@pookiepats]

read your emails dude

[@LenWoodward]

first

[@reppair]

Tip no.3. I think you can upgrade your knowledge and advice on estimates. See what uncle Bob has to say on the subject - kzbin.info/www/bejne/qYSoZ4tmZqqNZ5Ysi=gNiiGSVhAhrP4qd5 I've done "honest" estimates for the last ~5 years and it works as a charm (freelance and full-time job in a team). BTW the full talk is even greater, couldn't find a link though.