Much of Nick Cosentino’s career has been focused on the engineering culture of startups. This includes all things from writing code to managing teams.
Failure: Should You Fear It? Thanks for checking out this weekly article dump, and sorry it didn't make it out on Friday. I was out visiting family in Alberta and I didn't have enough time to get this post all set up. Better late than never! The theme for this past week seemed to be articles about failure. Not all of them, of course, but a lot of authors are writing about what it means to fail and why that's not always such a bad thing. Do we need to avoid all failures in order to be successful? Articles Stepping Away, So Others Can Step Up: In this article, Jonathan Bush discusses something that's often hard for leaders to do... Step away. It's difficult for many people to disconnect and have trust in their team to get things done. Trust should…
Great Leadership Reads Here's a collection of articles I've shared over the past week on social media outlets. There's a lot of great leadership reads this time around! If You Don't Treat Your Interns Right, You are Mean...and Stupid: This is a great post by Nancy Lublin that talks about something many full-time people share a common (and usually lousy) perspective on: interns. In my opinion, if you aren't going to treat your interns well, you shouldn't be hiring them. One key take away point from the article is ensuring that you treat your internship programs as something real and meaningful. Now, as a computer engineering graduate from the University of Waterloo and from being part of the leadership staff at Magnet Forensics, I've seen both sides of the story. Companies should treat their interns well, but interns should also realize companies…
A weekly summary of articles focusing on career development, leadership, startups and development. This is one BIG list!
Background I’m sure what I’m about to talk about here doesn’t just relate to programming–it relates to any team-based project where everyone works on a small portion of the big picture. My experiences are primarily geared toward writing code in teams, so try to find parallels in your own work/experiences if you’re not a programmer. Anyway, enough of that. When someone puts a lot of effort into something, they’ll often take great pride in the finished product. Of course, it’s great that they do! They’ve slaved away at something at work for days, weeks, or months, and it’s finally working/implemented. Other people are using it and it’s doing its job as expected. Awesome! What kinds of things could possibly go sour here? If you have experience working in teams to complete a project, you might have some ideas. Ownership You…
Background When you're starting work on a new project or organizing a team to accomplish a goal, there's often a foundation that needs to be established: How is your team structured? What software should we use to help us? How do we set goals? How do we measure our progress ... the list goes on. It's a common challenge that's met by anyone organizing a team or setting off to work on something. So do you copy what worked for someone else by using a cookie cutter approach, or do you wing it and see what happens? My approach when faced with two extremes is usually to aim somewhere in the middle. Cookie Cutters Being a copy-cat and using cookie cutters has some benefits. If something worked for some all-star teams at big successful companies, then why re-invent the…
A posting to summarize the articles I've shared on social media over the past week. There's a focus on motivation, leadership, and workplace culture.
