Monday, May 31, 2010
John Bristowe has posted a nice list of tips to get ready for any big conference. I'll let you read the details there, but here's a summary.
- Have a plan
- Bring a good backpack (I'll just add, don't use the conference bag during the conference - thousands of people have the identical bag and it's confusing)
- Wear comfortable shoes
- Bring lots of business cards (yes! You are here to meet people and people are here to meet you! Make it stick)
- be able to get by on crummy or no wireless
Give yourself time before, during, and after the event. You need to plan and make goals in advance. While you're there, go to talks, be open to serendipity (conversations, extra talks, booth visits) and don't forget to go to dinners and parties for vital face time and relationship building. Then you need to have time to follow up when it's over. This happens once or twice a year for most people. Putting an extra ten or twenty hours into it will make a HUGE difference.
Saturday, May 29, 2010
It's no secret that I'm not in my twenties. After all, I'm in my fourth decade of being paid to program. (To be fair, you enter that decade as you pass the doing-it-for-30-years mark.) I have gained a lot of experience in all that time, and not all of it is programming experience. I am slowly gaining wisdom and judgment in general. But am I losing things? Am I perhaps closed off to new experiences, or stuck in the mud? Is there anything you can in general conclude about a person because of their age?
I have two problems with that line of thinking. The first is that differences between any two individuals in a group are always larger than the differences between groups. I can easily find two 20-somethings who differ from each other more than either differs from a 30-something or even an 80-something. Women in general may be shorter than men in general, but I'm sure we all know a man who is shorter than most women or a woman who is taller than most men. What you know about the group doesn't necessarily apply to the individual. My second problem is specific to age - some age related effects are actually related to "you went to university in the 70s" or "you learned to code in the age of GUIs" more than to how old you are, others are actually about your life experience, still others your work experience. Two 60-somethings may not have gone to university at the same time as each other or learned to code at the same time as each other. That makes it even harder to generalize based on a single piece of information - when you were born.
A few months back, 'Dave' posted a series of myths about older developers and then debunked them. Do you find yourself believing any of these?
- Older software developers are more expensive
- Older software developers are less flexible and less capable of learning new
- Older software developers are less able to perform the arduous tasks of
software development (read: work long, painful hours)
- Older software developers are less mentally agile
- Older software developers are more jaded and cynical
My only issue with this list of myths is that it doesn't contain positive ones. It's also a myth that older developers are wiser, more tuned to business issues, better at talking to others, and so on. Some are -- I strongly believe I am -- and it takes a while to get there, but time passing isn't the only thing that brings about that change in a person.
I have to work with people a lot younger than me every day. Perhaps some of them think less of me because of my age at first. I'm pretty confident that doesn't last. If you're not an "older programmer" yet, I hope you aspire to be one someday.
Thursday, May 27, 2010
Update: fixed the link. Thanks, Hanako Izumi.
C++0x is finally becoming real to me. I started demoing some C++0x features over a year ago; but now here is Visual C++ 2010 and it's just packed full of goodness. Does it have everything? No. Does any compiler? Good question.
Here is a handy table from the C++ team about what Visual C++ 2010 supports. The MSDN blog redesign seems to have borked the table a little, but the colours should probably be all you need if you know that the last column is VC10. Use View Source if you must know more. Scott Meyers keeps a spreadsheet, and is nice enough to export it out to the public web, covering gcc and VC, with handy links to more details on the features or a substitute (usually something from Boost) you can use if it's not there. He has plenty of helpful links on the cover page, too. There's also a wiki with less detail, but covering more compilers.
If you're wondering about the state of the standard, and whether x is going to end up being A, B, or C, your best bet is to read Herb Sutter's blog. He posted when the Final Committee Draft (FCD) was text-complete, and a pointer to how anyone can comment on it if they wish to.
If you haven't been paying attention, now's the time to catch up!
Tuesday, May 25, 2010
When I started out in this industry (and I'm in my fourth decade of being paid to program) there was a definite culture of rudeness within it. Smart people weren't just allowed to be rude to not-so-smart people, it was expected. Being rude to others was how you proved you were smart, whether it was with a cutting insult thought up on your feet, or with a cruel proof of just where they had gone wrong. As a group we were especially fond of insulting those who weren't developers with brilliantly disguised insults they couldn't understand, or so the theory went. Who hasn't heard someone refer to "error codes" like PEBCAK or ID-ten-T?
But over the last generation or so I've noticed a switch. I hear the chair, keyboard thing still, but only self-referentially. That is after someone has asked for help, perhaps with a starting position of "I have found a bug in Windows", and then sorted it all out and realized they were doing something wrong, they may say "well it turns out the problem was between the chair and the keyboard after all, eh?". When I interview developers for a job at my firm, I ask about working with non developers (testers, technical writers, users, project managers) and I need to see (not just be told about) respect and interest for those people and those jobs.
Now not everyone feels that way. Meredith Levinson
asks if there is a still a place for the "I'm smart, I don't need soft skills" geek pride of old. Commenters point out that speaking truth to power is important, and those who won't be rude sometimes don't do it. David Starr
talks about how to tell someone that a thoughtless habit, like always coming late to meetings, is bothering you. I would skip the praise sandwich
, but I support the idea of pointing out the consequences of something another person may have thought had none. Interestingly, Susanne Biro
points out how people who are actively interested in learning soft or social skills can still be blundering about doing very rude things, apparently unaware.
I think in the end it's not that our industry has changed much. It's that people who are just starting out in it are often a bit rude. OK, sometimes they're very rude. But as they gain technical skill, many of them also gain the ability to take others into account and to work in teams. Those people get promoted. So now, hanging out with decision makers, with people who are allowed to represent their companies in public, with people who get paid to help other people get better, I mostly meet polite and interesting geeks. The rude ones probably still exist -- I just don't run into them very often. Which group would you rather be in?
Sunday, May 23, 2010
I have quoted
Albert Einstein here before, but only one quote. Amber Naslund
has found 14 nice quotes and connects them to social media issues. I'm sure you could find a way to connect those quotes to what you work on all day, too. I'm going to spend some time thinking about "Everything that can be counted does not necessarily count; everything that
counts cannot necessarily be counted."
Friday, May 21, 2010
The C++ team gave me a heads up about a neat new initiative called Hilo. Here's a quick description:
“Hilo” is a series of articles and sample applications that show how you can
leverage the power of Windows 7, Visual Studio 2010, and Visual C++ to build
high performance, responsive rich client applications. Hilo provides both source
code and the written guidance that will help you design and develop compelling,
touch-enabled Windows applications of your own.
The articles are on MSDN - the first is there now - and the code is on Code Gallery.
I like this section from the article:
The rich user experience of Windows 7 is best accessed through a powerful,
flexible language, and that means C++: by using C++ you can access the raw power
of the APIs for Windows 7. To build the Hilo sample applications, all you need
is Visual C++ Express and the Windows SDK for Windows 7, both of which are
available as free downloads.
Hilo applications show how to design and develop an application for Windows
7. But while the code showcases the APIs for Windows 7, it is not wedded to any
particular application framework. Instead, Hilo implement a lightweight common
application layer that directly uses and highlights the APIs rather than
obscuring them. This common application layer is used to support all of the Hilo
applications. It illustrates the best practices for developing Windows
applications, and while it is not complete—it was designed simply to provide the
features needed by the Hilo applications—it does show the best practices used in
designing re-usable frameworks and can be extended to provide additional
Looking forward to reading more!
Wednesday, May 19, 2010
A colleague of mine who is not near Toronto has a client in Toronto who needs .NET developers. They would like to start out with a contract position and it could become permanent if it's a good fit for everyone. Here's the job description:
Position: Senior Programmer / Analyst
Pay: $7,500 per month contract (negotiable)
Applicant must be an expert or proficient in:
- .NET Framework / C#
- .NET Services
- Microsoft SQL Programming
Experience in the following areas would be helpful but not required:
- Visual SourceSafe
- Mechanical engineering experience
The primary responsibility is to modernize a legacy C++ distributed application. This may include a redesign and possible rearchitect of the application. The final application should be an n-tiered application. The tiers would ideally be:
- WPF/Silverlight as the presentation layer
- A business layer with business components (C#) exposed via WCF
- A data layer
Where necessary, COM components can be preserved.
Other responsibilities include:
- Move image files from file database to SQL database
- Document the application
- Handle ongoing change requests.
Someone who moved from C++ to C# but didn't forget their C++ would be perfect. They are looking for more than one person so it sounds like a fairly meaty project. This is strictly onsite work, no remote work, which is why I mentioned where they are (east of the DVP; west of Pickering.)
Anything you email to me about this I will forward to my colleague who will in turn forward it to the Toronto folks. Good luck!
Monday, May 17, 2010
Have you seen this yet? It's a letter from Leonardo da Vinci (yes, that Leonardo da Vinci) to a prospective patron. He lists fully 9 paragraphs of way cool things he can do that are relevant to the warfare of the time (portable bridges, bombing strategies, stone flingers, ways of tunnelling into places and so on) and then mentions:
10. In times of peace I believe I can give perfect satisfaction and to the
equal of any other in architecture and the composition of buildings public and
private; and in guiding water from one place to another.
11. I can carry out sculpture in marble, bronze, or clay, and also I can do
in painting whatever may be done, as well as any other, be he who he may.
Given how well he followed through on those last two (this letter was written before his most famous works) you kind of have to believe all the siege/bombardment stuff too.
The article I've linked to has an image of the actual letter - not in English of course - and some lovely commentary on what makes it a good cover letter. It's not really a resume but it sure is a job-getting device. Apparently the Duke did indeed hire him - as a painter, not a fighter. And if you'd like to see it translated into modern day geekery, I spotted that too.
© Copyright 2019 Kate Gregory
Theme design by Bryan Bell
newtelligence dasBlog 2.3.9074.18820
| Page rendered at Thursday, October 17, 2019 6:48:22 PM (Eastern Daylight Time, UTC-04:00)
On this page....
Pluralsight Free Trial
Click Start a FREE 10-Day trial