I’ve come to the firm belief that writing detailed functional specs upfront for software projects is a total waste of time. Software is meant oto be used and in order to find out what it’s use is going to be software architects need use cases. writing specs is just moronic when you have no idea on how it’s going to be used
I’ve been working with a large project that has a lot of unmanaged MFC and C++ code, and new managed code using C#, C++/CLI with a many third-party libraries written in unmanaged code. Because of the complexity of the code, and sheer number of projects (>50 at the last count), I’ve been debating on using some scripting language to prototype and test code. I know Python, so I’ve started off with that. Unfortunately, Visual Studio 2005 does not have a good integration with the IronPython console. I tried getting the add-in sample to integrate with Visual Studio, but after wasting a few hours decided to use it without intellisense.
F# on the other hand has pretty good integration wit a REPL console, compiler and interpreter. Although, I know some functional programming, (doing some programming in Lisp, Haskell, and Boost.(Lambda|Bind|Spirit) in C++), F# seems to have an alien syntax. I’m pretty sure that after a few hours, I should get the hang of it. Probably, next weekend. Although its looking more and more likely that I’ll be at work this weekend again.
I do like this T-shirt though.
Brought to you via here.
I wish plain old C enums played nicely with CLS enums, or that I was smart enough to remember the nuances of how they differ.
A few days ago I blogged about how the Microsoft’s hostile takeover attempt of Yahoo! was reminiscent of the Black Hole Travel Agency books. Looks like Yahoo! has finally decided to fight back.
I used to think that of all the three major Internet players, Yahoo! would be the most successful, since it appeared that it had the knowledge of how to use the Internet for information and media delivery, plus it had the most experience. Was I woy off on this or what!
Live Writer is out of Beta. Although I think it was designed for Windows Vista rather than Windows XP.
All th blogging that I had done for the past two months seemed a excessive, so I decided that I was going to take a little breather, and let my thoughts gather. Unfortunately, any ideas for blogging topics that I have, are either incoherent or a victim of my procrastination.
So instead, I decided that I would simply write a bunch random notes, on things I saw today. just to let everybody, I’m still alive. I’m not kicking, but I am alive.
This is a blog post by a software engineering manager, about resume writing tips to getting past that 30 second look-over. I’ve read a lot of these resume tips over the past couple of years. The last time I updated my resume was about five months ago. In about a month or so, I’ll be updating my resume (something I do every six months or so). I’m not currently looking for a new job, but updating a resume every six months or so has allowed me to take an honest appraisal of where my career has been going.
My first cut of my resume is brutally honest. It’s so brutal, that I would call it resume self-flaggellation. This would not be a resume that I would send out, but a resume that would allow me to do a very honest self-appraisal of where my career is going. Depending on how I come out of that experience, I make a decision on what I need to do. My last experience, left me somewhat ambivalent about my career. I had some mixed feelings on where I wanted to be.I could’nt make up my mind whether I was happy or not. So I re-editted my resume into something that was more likely to get a second look and I looked around half-heartedly to see what was out there. Nothing came out of it. Landed a phone screen interview, but could’nt get past it. Dissappointed, I stopped trying.
Lesson learnt? In my opinion, that ambivalence really set me up for failure from the get go. Because, I had some mixed feelings, I was’nt really aggressive enough to go after what I wanted. I was’nt even sure what I wanted. Resume tips are all right, but if you really don’t have that drive for that something different, you’re job hunt is DOA.
End of March, I’m going to update my resume again in the same way. Let’s see where how that excercise ends.
First, Norway went after Apple for not allowing songs downloaded from iTunes, to be playable on the iPod only. Now, Belgium has decided that Goolge’s caching of information (that incidently is free) on the web is a violation of Belgian copyright. This is beginning to sound like a straightforward European governmental witch-hunt because they just can’t seem to make an alternative service. I used to think that the continuing European monopoly action against Microsoft was because Microsoft was guilty of monopolisitic practices, but now I suspect it was just because some beauracrat decided that lame legalism will constrain the competition.