Tag: manager

Team Theme – Weekly Article Dump

Team Theme - Weekly Article Dump (Image from http://www.sxc.hu/)

Articles

  • The Real Reason People Won’t Change: Admittedly, when I read this article on my phone the full posting wasn’t available to me. I was only able to read the first page of the article, but the concept was enough to get me interested. “Competing commitments”. Heard of it? I hadn’t but it seems to explain a lot. Competing commitments are, as you might have expected, commitments to things that are in conflict. The article has a ton of examples, but the concept of competing commitments offers insight as to why some people seem stubborn in their ways, despite everything else being lined up for success. A simple example might be someone who is a die-hard advocate of the project they are working on and really wants it to succeed. However, they’re actually inhibiting the success of the project because they aren’t comfortable with their role in relation to teammate. As a result, the team suffers and then the project suffers, but their alignment to wanting the project to succeed is in the right spot. Now that I have full access to the article, I’m certainly going back and reading through the whole thing.
  • Want to be Extremely, Wildly, Radically Successful?: I really appreciated the perspective of Joel Peterson in this article. There’s a million and one books and articles online about how to be successful. They all have titles just like this one. They’re all a bit over the top and unrealistic: “The one thing you need to do to be successful”, “The shortcut to success”, “5 simple steps to being the most successful human being in the universe”. There’s no shortcut to success. All the articles and books that offer information on being successful are doing just that: offering information. You need to make a habit out of doing things that make you successful. Live it. Day in, day out. And it’s not going to happen overnight.
  • The Problem With “There’s a Problem”: This is one my own, so it’s another shameless plug. This post was all about, in my opinion, the right way to tell someone about a problem. If you simply just tell someone that something is broken, doesn’t work, or isn’t right and that’s all that you do, you’re slacking. Everyone, especially in a startup, has a million and one things to do. If you’re about to offload some problem onto someone, at least do your part and get some context around the problem. Better yet, generate some potential solutions so that you’re going to people with solutions, not problems.
  • The Most Powerful Habit You Can Imagine: A colleague of mine shared this article earlier this week, and I felt I had to do my part to share it as well. In this article, Bruce Kasanoff outlines some traits to making your leadership skills more effective. By introducing some compassion and treating people like people, you can have a big impact. People will align more with you and want to work with you. It’s hard to resent your leader or manager when they’re the type of person who fights for you around the clock. You can greatly improve your team mechanics by not acting like an overlord robot.
  • Leadership Tips from The Voice: This article was a bit unique compared to the rest, but I thought it was a cool parallel. Jackie Lauer from Axeltree put this one together. She uses a music performer’s traits as a comparison to a good leader. The highlights? Be fearless. If everything you do is calculated to eliminate all risks, you’ll never fail, and you’ll never learn from it. You need to be a human with the people you lead. Know your strengths and your weaknesses. Build a team that’s strong where you’re weak.
  • The 6 Types of Thinkers to Seek for Your Team: Katya Andresen defines six variations of how people think and how they’re important in a team. She’s not claiming that you need six people (one with each way of thinking) to be successful but rather an individual can have a variety of these perspectives. The interesting part is that if you look at her list and compare it to your current team, you can probably fit each team member into one or two of those types of thinkers. Pretty neat!
  • The Town BlackBerry Built: Is Anything Left?: This isn’t an article… but a video! Our CEO of Magnet Forensics, Adam Belsher, is featured throughout most of this video. Myself and a few colleagues actually have some cameo appearances too, which I thought was pretty cool too. For anyone outside of Waterloo that hears about all the RIM/Blackberry talk, they often have a different perspective of the town than the people living here. Waterloo has an absolutely incredible startup community, and regardless of how good or bad Blackberry is doing, it’ll continue to thrive. As Adam said, it’d be silly if you’re looking to expand your team or business and you’re not even considering Waterloo.
  • 2 Mental Exercises For Battling “It Won’t Work” Syndrome: In startups (or any company really), generating new ideas is a big part of innovating. With any idea, there needs to be a choice to act on it or not. This article is about how some ideas are simply just dismissed without actually giving them a chance. it might be worth trying these exercises out with your team if you feel there isn’t a good environment for nurturing ideas.
  • Infighting is Toxic and Probably Running Rampant at Your Company: What is infighting and how is it killing your company? Let Daniel Roth tell you. In his article, Daniel talks about how competing against each other inside your company can be poisonous. Why not work together towards your common goal against your common competition? If you truly want your company to be successful, you need to put aside your personal agenda.
  • The One Belief That Is Holding Back Your Career: Like the infighting article, Fred Kofman‘s article has a similar perspective. Stop thinking about the goals of individual components of the company. If they are not working toward the common goal of the company, they are not operating effectively. An excellent example is given int he article: The aim of the defense of a soccer team is not to stop the other team from scoring. Their goal, like the rest of their team, is to win. Taking defensive action is how they accomplish that. However, if they’re down one point and the clock is running out, you can bet they won’t just crowd around their end trying to stop any more goals from being scored.

Remember to follow Dev Leader on social media outlets to get these updates through the week.

Nick Cosentino – LinkedIn
Nick Cosentino – Twitter
Dev Leader – Facebook
Dev Leader – Google+
Nick’s CodeProject Articles


Migration – Weekly Article Dump

Migration - Weekly Article Dump

Migration: Bye to the Pi

Well… it happened. If you checked in earlier this week, you might have noticed Dev Leader was completely down on Thursday. Quite a bummer… but the show must go on. Migration to a new host was necessary, but that wasn’t without some hiccups.

For me, having a site hosted was still a pretty new process. I had tried it a couple of times before, but running a web server that I controlled always felt better. Just more control I suppose. Migration started off sort of sour where I was required to re-install WordPress on my host a few times due to some technical difficulties… And of course, it was hard to sit still while I knew my site was down. Once I finally had WordPress launched, the only part of the migration that went smooth was having a backup of my site four hours before it went down. Talk about timing!

There’s silver lining in everything though, and this little migration blip was no different. My Raspberry Pi was a fun little box, but it wasn’t fast by any stretch of the imagination. Page loading times were a bit slow, and serving images could sometimes be terrifyingly slow. Now that the site is hosted, there should be a very noticeable performance improvement. Additionally, with the new host comes some additional reliability! That’s always awesome.

See? Migration wasn’t so bad after all, I guess! My list of things for any WordPress user to be doing regularly:

  • Back up your posts
  • Back up your comments if your readers are actively engaged in discussions
  • Back up the media you use on your blog
  • Export your plugin settings
  • Keep a list of plugins you have running

Even if you don’t have a plan for host migration any time in the near future, it’s always good to have the “worst case scenario” covered. The plugin BackWPup covers basically everything I mentioned above, so I’d recommend getting that setup if you don’t have any backup plan currently in place!

Articles

  • Feedback is the Breakfast of Champions: 10 Tips for Doing it Right: Anyone in a leadership position knows just how valuable being able to provide feedback is. Heck, anyone who is driven to improve themself craves feedback. Joel Peterson provides an awesome list of tips for being able to provide feedback. I’d say frequency, positivity, and confidentiality are among the top take away points from his list.
  • 10 ways to make your .NET projects play nice with others: First programming article in the list this week. I thought this one stood out because I think anyone working in a team has either heard some (most) of these or is trying to work through them. Troy Hunt has put together a list of 10 things that any developer working in a team should be conscious of to make sure their code plays well with their teammates. Number one on the list is the same as my number one. “Works on my machine” carries no validity. Why? Your customers don’t have your computer. It’s a frequent thing when working with the QA team and developers want to cover their butts… But it won’t cut it!
  • Only 13 percent of people worldwide actually like going to work: Had to share this one, because if the stat is real, it’s scary. It’s scary to think that almost 90% of people that go to work don’t actually like going. In Jena McGregor‘s article, this low rate is attributed to poor working conditions, job availability, and job engagement. On the bright side for us North Americans, we’re a bit higher at just under 30%. That’s still far too low for something we spend a majority of our lives doing. It’s important to find a company you can get behind, and I definitely lucked out with Magnet.
  • The New Science of Who Sits Where at WorkRachel Feintzeig shared an interesting article about seating in the workplace. I’ve shared some articles before about open concept offices and that I do enjoy working in them, but the seating perspective is pretty interesting. For example, changing your org hierarchy is one thing but unless people are changing their daily interactions, it won’t have that big of an effect. However, if seating arrangements are responsible for 40-60% of people’s daily interactions, simply moving people around will really stir the pot.
  • What is the Biggest Mistake Managers Make?: In John Murphy‘s article, he points out something that is probably less obvious than it should be. The biggest mistake a manager can make is focusing on the wrong things. He provides some steps to help align managers with the goals of their company to ensure that focus is in the necessary areas.
  • 8 strategies for successful culture change: Culture is something that is dynamic and always evolving within a company, but often there are things that are core to the company culture. What happens when you need to make some work culture changes? Michelle Smith shares some tips on how to approach a work culture shift.
  • Why Inspiring Leaders Don’t Sweat: Here was an article that hit home with me because I’m guilty of it. Panicking. Why is it bad if you’re panicking in a leadership position? The biggest problem is that your teammates will pick up on it and switch to a panick state too. It’s incredibly demotivating, and it’s usually at a time when motivation and inspiration is truly needed. In Steven Thompson‘s post, he talks about how and why to keep calm and lead on.
  • 3 Proven Ways to Make Tough Job Decisions: Jennifer Dulski discusses three approaches for helping make tough life and career decisions. At some point or another, most of us will be faced with making a decision in our career path that’s going to be difficult–difficult for you to decide or difficult for you to explain to those you’re close to. I think the “Sit With” approach is my favourite of the three.
  • 4 Ways to Have a Life Outside Your Business: This one should probably hit home with anyone working in a startup or running a business. Alexa von Tobel shares four tips for how to have a life outside of work and why having a life outside of work is necessary to be successful. I think something that’s often overlooked (somehow) is “me time”. I’m guilty of it too, but you get to a point when you’re not doing anything just for yourself. It’s great to be dedicated to your company and be passionate about your work, but it’s also importnt to step back, take a breath, and do something just for you.
  • 17 Things The Boss Should Never Say: Dave Kerpen has another great article on what not to say–this time from the boss’s perspective. Some of the worst ones in my opinion? Telling your teammates it’s only their problem (or not yours, at least) or being adamant about not evolving your perspective/processes. Some gems in there from quite a few business owners.
  • 9 Lessons From the World’s Best Mentors: This one is pretty quick from Chester Elton, but there’s a few different perspectives shared in here. Sone key points in my opinion are ensuring that you’re doing what you can to help others and not getting paralyzed by risk.
  • Key Reasons Delegating Is SO Difficult and What To Do About It: Most new managers and leaders have this problem. How do you delegate work? Perhaps you acquired your management or leadership position because you proved that technically you were very capable in your position. So how do you get others to do work you think you could be doing? Judith Sherven shares some insight on why being able to delegate is an incredibly important skill as a leader. After all, being able to grow as a leader means being able to effectively delegate responsibilities.
  • Want Greater Employee Engagement? Develop Intrapreneurs: In this article, Larry Myler talks about increasing employee engagement by developing intrapreneurs within your organization. It’s inline with what Tayun’s guest post was about the other week. Provide people autonomy and let them execute on their strengths. It’s a sure-fire way to increase engagement.

That’s it for this week! Hopefully there won’t be any more emergency host migrations any time in the near future (or ever again). Follow Dev Leader on social media outlets to get these updates through the week.

Nick Cosentino – LinkedIn
Nick Cosentino – Twitter
Dev Leader – Facebook
Dev Leader – Google+
Nick’s CodeProject Articles

You can also check out Dev Leader on FlipBoard.


v6.2 of IEF from Magnet Forensics! – Weekly Article Dump

IEF v6.2 from Magnet Forensics

v6.2 Release: Mobile Forensics Upgrade

I like to be able to use these weekly article dumps for little summaries of what’s going on in my work life, and I think this is a perfect opportunity to acknowledge our latest product update at Magnet Forensics. We just pushed out v6.2 of Internet Evidence Finder and we’re incredibly proud of the work we’ve done. Like any release we have, we pour our hearts into making sure it’s a few big steps forward. We’ve done our best to listen to customers and work with them to address any bugs, but we’re always trying to push the boundaries in our features.

Some of the new offerings in v6.2 of Internet Evidence Finder include:

  • Dynamic App Finder: We now offer a solution for recovering mobile chat applications that we may not have otherwise supported. This is a great discovery tool and has proved to be very powerful even in our early tests. Read more about it here. v6.2’s secret weapon!
  • Chat Threading: Visualize chat threads within our software as they look in their native applications. If you’re looking at a Skype conversation between two or more people, it will show up just like it does from within Skype. A lot less jumping between records to piece together a conversation.
  • L2T CSV Support: L2T CSV files can now be loaded directly into our timeline viewer.
  • Case Merging: Combine multiple IEF cases together or pull in data from TLN/L2T CSV files.
  • More Artifacts: v6.2 is no different than previous releases when it comes to adding new artifacts!
    • AVI carving
    • Hushmail
    • TOR chat
    • Flash cookies
    • Offline gmail
    • Additional Chrome support
    • … and more.

If you’re a forensic investigator, v6.2 is going to be an awesome upgrade or addition to your suite of tools. If you’re not, then check out Magnet Forensics to see what we’re all about and so proud of what we do. Congrats to Magnet on an awesome release of v6.2!

Articles

  • In praise of micromanagement: I’m still very early on in my career, so it’s difficult for me to have an opinion on this article and back it up. It’s a bit controversial, so of course I want to take the other side and disagree with it.There’s that, and I have some discomfort when it comes to Apple so I like to turn off when I see articles on Apple or Steve Jobs. Regardless, I thought that there was an interesting perspective in this piece to share, and maybe even if I can’t see it right now, others would benefit from reading through it. Is there a place for micromanagement? Can it be done right? Are people like Steve Jobs just an exception to an otherwise good rule?
  • The Myth of the Rockstar Programmer: Scott Hanselman says that rockstar programmers don’t exist–rockstar teams do. I completely agree. When your company is so small that you essentially don’t have teams, this might not hold. Maybe you have three developers and each one is a rockstar in their own right. That’s probably a it different. More often than not, you’re not working with one or two people developing a product for a company. It’s not about having one rockstar with all the programming super-powers take charge on the team. It’s about creating a team where everyone has their own strengths and weaknesses and then organizing them to operate at full efficiency. Teams. Not individuals.
  • Strengthen and Sustain Culture with Storytelling: This is an article that I can really align myself with. Nancy Duarte writes about something that’s often lost when small startups are transitioning into small businesses. It’s entirely possible some companies don’t even make it out of the start up phase because this thing is already going south. Storytelling. It’s important to be able to share stories with people as you bring them on board to your company. They need to know where the company has been and how it’s gotten to where it is. New hires need to feel like their part of the family as they are brought on board, and without conveying your company’s mission and values properly you start to lose that alignment.
  • Ignoring Your Test Suite: Another programming article here, but this post by Jesse Taber has some deeper lessons to be learned, in my opinion. The article talks about something not all programmers do, but should: write code that tests their code. This lets developers catch problems early on (because catching a problem now might cost a bit of time, but catching the problem later could be devastating). Running code tests regularly is a process that allows you to ensure the foundation of your software product is structurally sound. But what happens when you have flaky tests? What happens when you introduce a new failure and don’t bother to fix it? After all, you have 3000 tests, and you know why test ABC is failing anyway. Don’t put processes in place just for the sake of having them. Everything you do should be done for a reason, because your business doesn’t have time for anything else. Don’t enable poor habits. If you’re noticing problems in your process, identify why they are happening and look to get them fixed. Maybe you need to adjust your process because it doesn’t fit anymore.
  • Cameron Sapp – Recognizing The New Guy: This one is from me. I wrote up a little recognition piece about a colleague and teammate, Cam Sapp. I want to be able to write more recognition posts, but I started with Cam. He’s been a great addition to our team both from a technical and work culture perspective. All of Magnet is glad to have him on board.
  • Don’t Work For Your Boss, Work For Your Company: I thought that Ilya Pozin had written something great when I cam across this article. Hierarchies in the workplace can often cause disconnect and disengage employees. So why do we have them? I’m not against hierarchies–I think they serve a purpose. However, I think necessary measures need to be put in place to ensure that hierarchies aren’t detracting from the company’s goals. In this article, Ilya says to not work for your boss. Your goals at work should not be to satisfy individuals or only do things for your boss so you can get your promotion. Align yourself to the company values and the mission of the company. You’ll remain engaged and happy to do the work you’re doing. In the end, if you’re not happy doing work that’s aligned with your company’s mission, vision, and values, you might be in the wrong place.
  • Creativity and the Role of the Leader: This article discusses where ideas come from and how leaders fit in to the grand scheme of things. The traditional mindset is that ideas come from the top and then are pushed down to employees to carry out the work necessary for bringing the idea to fruition. However, it’s increasingly more common where ideas are actually generated by employees, and it’s the responsibility of the leader for nurturing idea creation and ensuring that ideas that are aligned with the company’s mission can succeed.
  • Will Your Firm Endure?: In this article by Tim Williams, I took away two key points. In order for your business to be absolutely sure it can endure, everyone needs to be viewed as replaceable. I don’t mean in the sense where we can trade John for Joe and not care because we don’t value human qualities, I mean strictly from the skills and responsibility aspect. There shouldn’t be instanced in your business where if an individual were to disappear one day your company wouldn’t be able to carry on. The next is acknowledging strengths and weaknesses. When people have some obvious strengths, they have weak areas too. There’s nothing wrong with that. It’s normal. Make sure your teams are constructed of people with complementary skills.
  • Dynamic Programming with Python and C#: Another article from me, and another programming related post. This my follow up to a post about C# and Python integration that seems to have been received really well. It was a cool little experiment for me to take Python and C# and have them working together in my favourite IDE, but on top of that, I was actually able to learn a bit about C#’s “dynamic” keyword which was new for me. If you’re familiar with either of C# or Python I recommend checking it out. There’s some pretty cool stuff you can do, and I’ve only scratched the surface.
  • To Find Success, Forget Your PrioritiesClaire Diaz-Ortiz says that priorities are too general. We all have priorities, but how many of us are seeing ourselves achieve what we’d like? Claire suggests forgetting your priorities and breaking them down into goals you can achieve. By having conrete action plans, you can execute them properly.
  • Personality Tests: Modern-Day Phrenology: Ron Baker shares his perspective on why personality tests don’t have a place at work. He goes as far as calling them meaningless, but I believe his main argument is that simply siloing people into personality types is pointless. To that end, I agree. I thought this article had great timing because I’ve been discussing personality tests with our HR manager at work. I came across this article right before doing a personality test with her and we decided a few things. Firstly, if the results of the test don’t make sense, then don’t go any further with it. This means that either the test you’re using is flawed or perhaps you don’t understand the test. Regardless, how can you take action on something you don’t understand? We both agreed that simply identifying traits was useless on it’s own, so I think we agreed with Ron on this one, but we weren’t stopping there. The basic act of identifying personality traits had us sparking conversations about how our personalities were different and how acknowledging these differences could influence our interactions. Essentially, it was hard to just silo ourselves into a particular personality type without thinking about and acting on what we were observing. In the end, identifying personality types and sticking someone into some cookie-cutter process for it means nothing. The tests are all about ganining insight and understanding so that we can choose where to go from there.
  • How Open Should a Startup CEO Be with Staff?: Coming from a startup, this was another interesting article. Mark Suster writes a semi-controversial perspective about CEO transparency. The norm is that expecting CEO’s to share every bit of details with the employees achieved perfect transparency and makes everything better. Mark says this definitely isn’t the case and provides some excellent examples where total transparency came back to bite. It’s all about balance. Transparency is great,but total transparency is often too much for most employees to handle on a day-to-day basis.

Follow Dev Leader on social media outlets to get these updates through the week.

Nick Cosentino – LinkedIn
Nick Cosentino – Twitter
Dev Leader – Facebook
Dev Leader – Google+
Nick’s CodeProject Articles

You can also check out Dev Leader on FlipBoard.


Movember Prep – Weekly Article Dump

MoMagnets - Magnet Forensics' Movember Team

Movember Preparation

You might think we’re a bit early on this one, but at Magnet Forensics we’re going to take Movember to a whole new level this year. If you’re not familiar with Movember, you may want to head over here and get a rundown of the history of it. Movember started in Australia between a group of people who wanted to (somewhat jokingly) bring the moustache back into style. The next year they started getting people to grow mo’s for causes. Now people participate in Movember to raise awareness for men’s health, and it’s bigger than ever.

Our team members of MoMagnets have started discussing the various styles of mo’s that they’ll grow this year. It looks like there’s going to be some intra-team competition to grow the best mo. The top contenders? It’s looking like:

Matthew Chang - Movember

Matthew “The Chang” “Changarang” Chang sporting a well-groomed black moustache. Although it’s a standard ‘stache, the care put into keeping this beauty mo in tip-top shape is obvious. Can he do it again for this Movember?

Cameron Sapp - Movember

Cameron Sapp showing off a rock solid handle bar mo. The bars on this ‘stache are so impressive that it almost gives the illusion that this mo is taller than it is wide. Wait… is it?!

Check out the MoMagnets page and keep track of us! Please contribute what you can to help raise awareness for men’s health.

Articles

  • Python, Visual Studio, and C#… So. Sweet.: First one on the list this week is the post I put out on Monday about using Python, C#, and Visual Studio all together. It’s definitely for the developers out there, but for those of you who aren’t programmers, it’s still interesting to see how PyTools and IronPython have bridged a gap between C# and Visual Studio. I was pretty happy with the number of people who responded on social media and thought that it was a good read. The tweets actually led me to find a related post by Scott Hanselman from earlier this year (that I wish I saw sooner). My article has also received some pretty good visibility at Code Project which I’m excited about. Feel free to check it out over there too (people seem more likely to engage in discussion at Code Project versus on my blog)!
  • Want To Build A Business? Lead With Trust: David Hassell wrote an article that really hit home with me. Having a successful business means crafting a team and culture built upon trust. It needs to be the foundation of your team. Having high levels of trust makes everything else in the business come together more easily, but lacking trust can really make everything fall apart. Teams need to trust their leaders, and leaders need to trust their team members–it goes both ways.
  • Amazon CEO Jeff Bezos Had His Top Execs Read These Three Books: John Fortt discusses his interview with Amazon CEO Jeff Bezos. Now while I don’t read as much as I should (and I’m consciously trying to get better at it), I thought this little list of books might be great to keep my eye out for:
  • Confidence ‘boosts pupils’ academic success: I thought this article was a great find. It’s primarily around research that’s shown confidence plays a big role in students’ success, but I believe it applies outside of the realm of formal education. As a leader or mentor, I think it’s incredibly important to instill confidence. You want your team members to know you trust them with what they’re doing. They need to know they can make mistakes and learn without having to be punished for doing so. Having that confidence is going to be what makes them successful.
  • Leadership Lessons From LEGO: What do leadership and Lego have in common? A whole lot according to John Kotter. Consider innovation (get creative with those bricks!), overcoming challenges (can’t find that piece you were looking for?), team work (building things with friends is way more fun), and quality (it’s as good as you make it). It was an unexpected article for me to stumble upon, but I thought the parallels were interesting!
  • The Four Most Powerful Lessons in Management: Joel Peterson has some great points on being a successful leader or manager. Among them, putting actions behind your words, bring the right people on board (noticing a trend with having the right people yet?), and having a meaningful mission.
  • What is a Thought Leader?: I found myself asking this question at one point, which is why I wanted to share Daniel Tunkelang‘s article. It seems straight forward really. It’s important to have an area of expertise in the ideas you want to share, and it’s important that the things you’re sharing have meaning. In my case with Dev Leader, I certainly haven’t mastered leadership and programming, but I’m sharing the ideas that I’m hoping will some day get me there.
  • 17 Things You Should Never Say to Your Boss: This was definitely a great read. At first, I started thinking “How could anyone in their right mind say these things to their boss”? But then I realized I had actually heard some of these things (or similar things) and it really got me thinking. Dave Kerpen has put together a great list, and although it’s humourous, it’s still something important to watch out for. Just in it for the money? Not your role? Some people need to get a grip or find something else to do in their career.
  • Why These Happiness “Boosters” Might Actually Make You Feel Worse: Gretchen Rubin shares some ideas on why certain things we do to make us happier may actually be counter-productive. One interesting one I thought was the idea of your attitude shaping your behaviour may actually be your behaviour shaping your attitude. On weekends I often hang around in a pair of shorts until I have to head out of my condo. If I got in the habit of being prepped to leave the house and be productive from the beginning of the day, would I find that I’m actually more productive? Worth trying!
  • What Makes Developers Really Great: Deane Barker shares his experience with a software developer that was giving off some bad vibes. So what’s a good developer? Is it just someone who can code? Do they need to know all the latest and best languages, dream in code, and have four computer science degrees? It certainly helps (and I don’t think many would dismiss it), but the one thing that’s really important is their attitude and ability to work in their team. Check out the comments on that blog post. If you’re working on a team and you can’t fit in the team, you’ll bring the whole team down. This means if you’re all soft skills and no hard skills, you can’t contribute squat. If you’re all hard skills and no soft skills, you’re going to be a road block to your team. You need to have both to be a really great developer.

Remember to check out the MoMagnets page! We’d really appreciate it. Follow Dev Leader on social media outlets to get these updates through the week.

Nick Cosentino – LinkedIn
Nick Cosentino – Twitter
Dev Leader – Facebook
Dev Leader – Google+

You can also check out Dev Leader on FlipBoard.


  • Nick Cosentino

    Nick Cosentino

    I work as a team lead of software engineering at Magnet Forensics (http://www.magnetforensics.com). I'm into powerlifting, bodybuilding, and blogging about leadership/development topics over at http://www.devleader.ca.

    Verified Services

    View Full Profile →

  • Copyright © 1996-2010 Dev Leader. All rights reserved.
    Jarrah theme by Templates Next | Powered by WordPress