
Cesar Aguirre
Editor at Xataka México
Articles
-
3 days ago |
medium.com | Cesar Aguirre
Long 300+ words stories with valuable information. Follow publicationI had to rush to the ER with a loved oneDuring a recent hospital visit, I found inspiration to write. To keep my mind busy and productively distracted while waiting for doctors to see a loved one, I took out my phone and started to jot down ideas. Ideas of how I could calm down and ideas of how hospital visits might look in 2035.
-
4 days ago |
medium.com | Cesar Aguirre
I know because I had one as a coderA stressful job can take a serious toll on your mental health. I know because I’ve had one as a software engineer. In that job, we were chasing our own deadlines, our clients’ expectations, and local government regulations. We were late all the time. Everyone blamed the Development team. Leaders constantly pressured us. Working after hours was normal. We called them “Miracle Nights.” In one night, we did way more than we did in an entire sprint.
-
5 days ago |
dev.to | Cesar Aguirre
I originally posted this post on my blog. Did AI kill the tech interview? Truth is hiring and interviewing have been broken for years. There wasn't much left to kill. In over 10 years, I've witnessed all types of interviews: casual conversations, interrogation-like conversations with rapid-fire questions, take-home coding exercises, and the infamous LeetCode exercises. I asked Phind and Copilot to solve an interview exercise. I might or might not have been asked that exercise when applying to a FAANG.
-
6 days ago |
medium.com | Cesar Aguirre
Coding tutorials and news. The developer homepage gitconnected.com && skilled.dev && levelup.devFollow publication#4. — QA only caring about colors, alignment, and fonts#1. A micromanaging boss. Why trust your team members when you can ask them every 5 minutes how they’re doing? #2. A spaghetti-style crappy codebase. Why use good names and focused methods when you can copy-paste code and leave outdated comments all over the code? It’s faster that way, right? #3. Working on something nobody will use.
-
1 week ago |
dev.to | Cesar Aguirre
My go-to guide to refactor a piece of code (or while reviewing code): Scroll through a piece of code to find blocks that make you to stop and read twice. There's something to refactor there. Something needs to be better explained.
Try JournoFinder For Free
Search and contact over 1M+ journalist profiles, browse 100M+ articles, and unlock powerful PR tools.
Start Your 7-Day Free Trial →