[code review]
my software engineering internship
“And, when you want something, all the universe conspires in helping you to achieve it.” — The Alchemist
Boy, the universe sure wants me to win to put me in the position that I’m currently in. I am finishing up my software engineering internship at a startup made up of the right people to take their idea far in a space that I am versed in.
Get i s a’s stories in your inbox
Join Medium for free to get updates from this writer.
I’m targeting these tips to future interns as well as summarizing my journey. Do note that I came into this great opportunity just as I finished coding school and with little experience whatsoever developing in the wild — zero to 100 in the blink of an eye. In no particular order, here are some high level points of what I will take with me from my internship throughout my coding career:
Tools & Trade Tips
From the start, each day presented its own fun-filled challenges from bootstrapping my local environment for the first time to working daily inside my IDE. Using the tools on a daily basis for real world application with direction from my senior developers (sr. devs) was absolutely priceless. Like learning all kinds of handy git commands (right now, my favorite is: git checkout — — . ).
I observed how the sr. devs work and how they communicate, taking tips and cues where I could. One of my sr. devs really took the time to run through his developing style step-by-step. He showed me how to take a task, incrementally break it down, and quickly prototype the wanted behavior to get the ux and code feedback needed to polish my work. Sounds easy right? Well, not when you’re facing a maze of unfamiliar frameworks, libraries, and custom architecture. plus deadlines. plus mentally absorbing it all. plus plus.
Aside from reference docs and other helpful pages I’ve bookmarked in my browser, I even made a Pinterest board on the articles my sr. devs had me read.
Best Practices in the Real World
Being a proverbial blank slate, I was able to take in lots of the moving parts of software development. I read as much code as possible with my sr. dev pointing out what ideal code looks like…and what code looks like when a deadline is looming. Technical debt is a compromise between what we want and the actual time to deliver it. Creating tests is also something that can’t be done for every. little. thing. Test when you need to test — like if you’re relying on an API service, or asynchronous calls that may overlap, or creating a custom service the whole application relies on. I also found that having something down is often more valuable than thinking about one’s approach to solving the problem. For example, if the you found a way to the solution, take that way first, then discuss together on the next steps or a possible better approach.
Code Review Hurts So Good
It’s like walking around naked for the first time at Baker Beach. Or that viral video of a bunch of strangers meeting for the first time and slapping each other. Once the first review is over, you want more. Code reviews are essential to your growth as a developer. You can wrap deep-dive discussions around a certain block of code, you can defend your reason as to why you chose your implementation. My first review was crushing, waiting for someone to review my code knowing that it was probably trash. Then, with every review, the syntax corrections became less and less and the concerns became more about approach and reasoning. Plus, sometimes, it can help surface something else that needs attention in the code base (anti-patterns, data marshalling, etc.).
Software Development is Communication
From ticket tracking on the agile board, to code reviews, to the daily chatroom interaction, being successful is about communicating well. At times, especially early on, I found myself blocked trying to grok sophisticated concepts that I needed to understand in order to get my task done. Speaking up with just even a ping inside the dev chat has helped me save hours of rolling around in my own mind. Someone, when they had a moment, chimed in and gave me better insight as to where in the code base I should be tapping into. Brainstorming with the product manager as to what the expected deliverable should be, and even chatting up during Happy Hour about some of the things I found poignant during the week has elevated my code immensely.
Getting Familiar With Software Development Processes
There are so many moving parts when developing software. It was good to be immersed in it all as part of a start up. Watching a tracking board come to life for sprints and managing my own feature’s swimlane was a great exercise in understanding time and cost in software development. Managing expectations and expensing time against issues that I was working on was an eye opener. It showed me how much time I actually spent discovering more areas of the codebase vs. thinking about how to approach my assignments vs. actually writing code.
I was lucky enough to be able to take part in design meetings, and watched how both my Product Manager and Sr. Dev worked well to layout our next steps. They converged the company’s vision with client feedback and guided the development team to further sophisticate the software. They have created a software that clients immediately gravitate to, and continuously update it with more tools that empower users to get more done. To be able to listen in on the lively discussions when they scoped things out was a valuable lesson; class was very much in session then.
QA is a Labor of Love
Testing an app with real world test cases in mind sure helps when having to click every button. That’s all I have to say about QA, just know, I’ve gotten realllly good at it.
Bring Value and Expertise In Other Ways
Coming in, I was very much novice in my way of thinking with regards to software development. What I did understand very well was the space my company was in, and I made sure to provide as much value to them as they were providing me. It could have been during casual discussions about a specific business process to finding bugs in the features that we were preparing to ship. I did my best to provide strong input, and give back to the team that gave me this opportunity to shine.





