Architech Do’s and Don’ts: A Co-ops Guide

As a Software Engineer Co-op at Architech, I've picked up more than just technical skills. For all newcomers to Architech, I’ve made this short guide to help you settle in...
Architech team members laughing

Hi, my name is Eli-Henry Dykhne. As a Software Engineer Co-op at Architech, I’ve picked up more than just technical skills. For all newcomers to Architech, I’ve made this short guide to help you settle in. Without further ado, here are my Architech Do’s and Don’ts! 

Do: Grab a protein bar from the middle drawer of the kitchen in the morning for a filling breakfast. If youre like me and don’t always eat breakfast, eating a bar after you arrive can be a much more pleasant experience than forcing yourself to eat when you don’t want to, or being hungry (or hangry) until lunch. 

Team having a stand up

Don’t: Go into overlong explanations during standup. Since standup is for brief updates, indepth discussion of your work should be stowed for after the meeting unless youre directly asked for it. 

Lunch and Learn Presentation

Do: Come to the lunch & learns and lightning talks to take advantage of the opportunity to learn something that might be outside your field of work. It’s also often a great chance to see what other teams have been working on or learn about events you were unaware. 

Don’t: Assume that your lead developer knows the answer to every problem. They‘re not your TA and have not seen the “answer sheet”. When working with new libraries, it’s entirely possible that you have the most experience with it on your team.

Two people collaborating on a computer

Do: Update your timecard daily. Trying to remember what you did on Monday while filling out your timecards on Friday is rarely an easy task. For those who ignored the above advice, checking your commit history for each day is often a good way to jog your memory. 

Don’t: Be afraid to ask for help. In this industry, theres almost always someone in the company who has experienced the same problem you‘ve run into. If you truly seem stuck, look to someone who may have worked on something similar. After all, one of Architech’s core values is “Be Open and Collaborate”. 

I hope my guide helps as you get to know the rest of Architech! 

 

Photo of Henry

Software Engineer Co-op Student

Eli Henry is a Computer Science student at the University of Guelph, with a passion for cloud technologies and Machine Learning.

We currently have Co-op opportunities for Summer 2020, so if you’re interested in joining us email talentandculture@architech.ca to learn more!

Get in Touch