Field notes,
in progress.
An irregular journal of software, leadership, and the occasional rant. Some pieces are practical. Some are me thinking out loud and hoping it’s useful to someone else.
Two years already
Two years ago
Read piece ↝
How to improve communication with your boss
Good communication allows many life situations to run smoothly. However, there are certain relationships that deserve extra attention, such as the relationship you have with your boss. You and your boss have drastically different roles, and when each of you fulfills these roles with a hard working and understanding attitude, you'll both feel fulfilled.
Read piece ↝
Take control of your next interview
Find Out What YOU Want to Know
Read piece ↝
Finding purpose at your job
Staring at your monitor at 9 AM (or earlier), already counting down to 5 PM? (or later) Feeling like you're just another cog in someone else's machine?
Read piece ↝
7 ways to combat work stress
Work stress in tech isn't just about tight deadlines or difficult stakeholders. It's about context switching between fifteen different priorities, debugging production issues at 2 AM, and trying to maintain code quality while everyone wants everything "yesterday."
Read piece ↝
Dealing with gossip in the workplace
Workplace gossip is like technical debt — it accumulates slowly, seems harmless at first, then suddenly becomes a massive problem that affects everything from team velocity to code quality. The difference is that gossip spreads faster than a memory leak and can be just as destructive to your work environment.
Read piece ↝
7 strategies for embracing change in the workplace
Change in tech happens fast. New frameworks, shifting priorities, team restructures, platform migrations — if you're not adapting quickly, you're falling behind. The question isn't whether change will happen; it's whether you'll be ready when it does.
Read piece ↝
Dealing with rejection during your job search
Getting rejected during a job search sucks. There's no sugar-coating it. But treating rejection like a debugging session instead of a personal failure changes everything about how you approach your job search.
Read piece ↝
How to work with difficult people
Every tech team has them: the developer who never documents their code, the PM who changes requirements daily, the manager who schedules meetings during your deep work hours. Difficult colleagues aren't just personality conflicts — they're system failures that affect team performance and your professional satisfaction.
Read piece ↝
13 Practical Ways to Live Your Dream(s) Without Quitting Your Day Job
You want to build that SaaS idea, launch a tech consultancy, or transition into machine learning. Meanwhile, you're debugging legacy code and sitting through status meetings. The gap between where you are and where you want to be feels overwhelming.
Read piece ↝
How to Command Respect From Others
Respect in tech isn't about hierarchy or titles — it's about competence, reliability, and professional judgment. The developers who command genuine respect aren't necessarily the loudest in meetings or the ones with the most GitHub stars. They're the people others trust to make good decisions, deliver quality work, and handle difficult situations professionally.
Read piece ↝
Read this before you reject a job offer
Getting a job offer feels good, even when it's not the perfect role. After weeks of interviews and rejections, there's validation in being chosen. But saying yes to the wrong opportunity can set your career back more than staying in your current role or continuing your search.
Read piece ↝
Strategies for Weekend Job Hunting
Most job search advice assumes you're unemployed with unlimited time to apply and interview. But if you're currently employed in tech, your job search happens in the margins — evenings, lunch breaks, and weekends. The challenge is making meaningful progress when you only have fragmented time.
Read piece ↝
The Secret to Applying for Jobs when You are Underqualified
Most job postings in tech read like shopping lists written by someone who's never actually done the job. "5+ years React, 3+ years Node.js, experience with microservices, knowledge of Kubernetes, familiarity with machine learning, startup experience preferred." It's the technical equivalent of asking for a unicorn.
Read piece ↝
Leaving a job gracefully
Leaving a job well is just as important as performing well while you're there. In tech, your professional reputation travels fast — the industry is smaller than it seems, and people move between companies frequently. The developer who burns bridges today might find themselves interviewing with a former colleague tomorrow.
Read piece ↝
How to write a great resume
Your resume is a strategic document, not a career biography. In tech, where hiring managers scan hundreds of resumes for each position, yours needs to communicate value quickly and clearly. The best technical resumes don't just list what you've done — they demonstrate the impact you've made and the problems you've solved.
Read piece ↝