#Career
28 notas · última:
Why system design is my favorite interview
The post argues that system design interviews reveal the most signal in an hour, because they test working design, judgment, questions, and tradeoffs while reflecting real engineering experience.
6 books engineers should read
The post argues that books give engineers deeper, more practical guidance than blogs or videos, and recommends six titles for everyone from interns to senior engineers based on teamwork, ownership, process, and decision-making.
Networking is easy, fun, and probably not what you think it is.
The page argues that networking is not limited to tech events; it happens mainly through everyday human connections, and tends to create opportunities when there is curiosity, kindness, and openness.
3 Harmful Beliefs That Destroy Software Developers Careers
The text points to three beliefs that hurt the careers of developers: trying to learn all languages, confusing long hours with productivity, and ignoring networking.
How to Level Up Your Dev Game
The author says her career improved by getting involved with the community, experimenting with practices, writing a blog, going to conferences, giving talks, creating a meetup, cultivating connections, and setting aside time for rest.
Don't Ask Anyone To "Be Your Mentor"—Do This Instead
The post argues that mentorship grows from genuine questions, interest in the other person, mutual help, and follow-up on advice. It also says books can function as mentors.
37 Tips from a Senior Frontend Developer
The text brings together career and practice advice for frontend: mastering fundamentals, practicing, asking for help, communicating value, learning continuously, and collaborating well with the team.
Lessons learned in 35 years of making software
Jim Grey says 35 years in software taught him lessons about simplicity, frequent delivery, visibility, networking, willingness to learn, and focusing on relationships and power.
How To Quit Your Job And Become A Freelancer
The text argues that leaving employment for freelancing begins by choosing what you like to do, turning it into an offer for multiple clients, and setting up a simple website to present services, portfolio, and contact.
Stuck in a rut? 5 tips to get your first freelancing gig
The text says that starting to work as a freelancer is usually difficult and that the safest path is to keep your job and act gradually, using five steps to get the first jobs.
What NOT to do while looking for a job
The post lists job-search pitfalls to avoid, including being too location-specific, overemphasizing certifications, appearing like a loner, criticizing a former employer, and using a generic resume objective.
From Software Developer to Software Engineer
Gergely Orosz collects two takes (Ian Brayshaw, Hartley Brody) on what separates a software engineer from a developer, landing on iteration and understanding-why as the path between the two.
Defensive Driving For Your Career - Stay SaaSy
The post says career progress depends on making your work visible, correcting false claims, avoiding jealous managers, and keeping enough leverage to negotiate pay and title.
The Next Two Years of Software Engineering
Addy Osmani lays out five open questions on how AI reshapes software engineering through 2026: junior hiring, core skills, the developer role, specialization, and education.
45 Creative Resumes to Seize Attention, Vol. 1
Hongkiat rounds up 45 unconventional resume designs, from one printed on a T-shirt to one folded into a 3D box, pitched as ways to stand out in a crowded hiring process.
About Brajeshwar
Brajeshwar Oinam traces his career from a floppy-disk design test in a Mumbai internet café in 1999 to Chief Product Officer roles spanning cricket media, mobile dating, retail supply chains and climate tech.
Unpopular Opinion: I stopped coding on weekends and my career got better
A senior developer describes closing the laptop every weekend for a year, and how the boundary sharpened his focus, made him a better colleague, and led to a promotion.
12 Hard Truths About Coding I Learned the Hard Way After 10+ Years
Twelve lessons from a decade of coding: estimates are guesses, seniority means more meetings, and almost every failed project traces back to a communication problem.
IC work is the new career flex
Elena Verna argues that AI makes high-impact individual contributor roles possible again: one person can now run projects end to end, reduce coordination overhead, and deliver business value without a team under them.
IC vs Management: A Longer Career Than You Think
The IC-vs-management decision feels permanent when you think in 10-year terms — but in a 30-40 year career, it's far less binary than it appears.
Working the Human System Within Companies
00:38:11 — Working the Human System Within Companies
Invisible Work Isn't Valuable Work
00:36:27 — Visibility: Invisible Work Isn't Valuable Work
Give-First Mentality Over Transactional Networking
00:30:37 — Give-First Mentality Over Transactional Networking
Four Groups Every Network Needs
00:29:23 — Four Groups Every Network Needs
Separating Technical and People Work Causes Crisis
00:14:01 — Separation of Technical and People Work Causes the Crisis
Peter Principle
"In a hierarchy, every employee tends to rise to his level of incompetence."
How I landed a dev job that didn't exist
John Sonmez says he turned a QA lead opening at HP into a developer role by working closely with developers, earning their support, and creating a role the company had not posted.
A Guide for Young People: What to Do With Your Life
The page argues that young people cannot know their future path, so they should prepare by building skills, tolerating discomfort and uncertainty, avoiding distraction, and becoming trustworthy.