Contents tagged with culture
-
You have a people problem, not a technology problem
[This is a repost from my personal blog.]
-
Why typical software design isn't common
As my contract gig ended, I started a new job where I've assumed the role of technical architect. It's a little like a cross between a development manager, development lead and traditional architect role. I'd like to think that it plays to all of my strengths, but I suppose I'll have to still demonstrate that!
-
5 Ways to surround yourself with awesome
[Repost from my personal blog.]
-
The problem and opportunity with accountants' view on software people
[Note: This is a repost from my personal blog.]
-
Performant: Stop making up words
People need to stop saying "performant." If it's a word at all, it's a noun synonymous with "performer," like an actor. Even if the construct was a real word, it wouldn't indicate whether it's a negative or positive thing. Something can perform well or poorly... this word would only describe that it performs.
-
Five things to remember when trying to change a company
One of the recurring things I've seen at companies large and small is that they often have really great people who don't necessarily have the breadth of experience to push processes in the "right" direction. It's happening a lot less in software circles than it used to, in part because people move around so much, and they build big boxes of best (or better) practices. Still, some people will only have experience moving between suboptimal environments, some will have long-term engagements that simply don't expose them to new things, and others will be the kind of stakeholders that by default won't expose them to alternatives (specifically, small company owners).
-
Today's ideal developer
Scott Hanselman wrote a short blog post about developers vs. Googlers, but I really love where that inspired Rick Strahl to go. Having been in a lot of positions to hire people over the years, I think Rick really goes in depth with regard to skills, career development and the market reality of what we need out of people.
-
Everyone else is doing it (incorrectly)!
[This is actually a repost from my personal blog, but I think the technical audience might “dig” it as well.]
-
One interface to rule them all
I'm not shy about telling people that I'm not much of a computer science kind of guy. It's not that I don't respect computer science or understand it, I'm just not one to get academic over it to the point of not building anything. And while I can't always remember what the hell SOLID stands for, I do remember that the "I" stands for the "interface segregation principle." It says, "Thou shalt not force everything to use one interface, because specific interfaces are better."
-
A year of remote working
[Note: I originally posted this on my personal blog, but it occurs to me that it’s likely something of general interest to software developers. -J]