Home | About Me | Opinions | Photography | Ketsugō Jūjutsu Résumé | Contact | RSS |
Projects | Résumé (PDF) | LinkedIn | Books | Transcript | Links |
As long as I can remember, I have been tinkering with computers. I can remember playing around with the operating system as a child, trying to see what was inside the guts of it, and of course I can remember playing many games to suit my interests. Computers have sparked my imagination for a long time. Being a software engineer was the adopted career of my father — after starting off in the music business — and when he saw my interest, he introduced me to the world of writing programs.
Even before high school for that matter, I was fascinated with how the bits of the operating system fit together, so I often played around, making things like terminal applications using Visual Basic, creating new MS-DOS console fonts, and implementing the UNIX ls command for DOS. It was only logical, then, that my friend and I would petition our high school to introduce a C programming course — which they did! It turns out one of the math teachers was fluent in C and C++, and so after studying C for a year, we asked them to add a C++ class. Almost every student from the C class joined the C++ one as well. For our final project, we made a top-down racing game, which was incredibly fun to make, and my friend and I have been writing software professionally ever since.
Only by surrounding yourself with smart people can you really understand how little you actually know. Yes, I already knew how to write software in C and C++, but when I got to Northeastern, they wanted well-rounded people to graduate from the university. I honestly didn't know how to really study until about half way through my time there, and I give great credit to Northeastern for really teaching me how to learn. There, I focused on compiler design. I feel knowing what the machine is doing as much as possible yields the best code, even at the higher levels. I always loved the science and precision that goes into writing a compiler.
Northeastern also introduced me into the professional software development world with their co-op program. This is actually the reason I chose to attend the College of Computer Science (CCS — incidentally, the “nation’s first computer science college.”1). To this day, I’m still so proud of the colleagues I met at Rational and Availant, and the work we did on ClearCase and IBM AIX high availability, respectively. It also (in combination with CCS) gave me exposure to nearly every form of UNIX and Linux.
Almost immediately after graduation, the “dot com bubble” burst. My peers had gone from companies trying to get us to drop out of college with signing bonuses, to nobody returning phone calls checking for openings. It was tough — I still have a list of companies I cold-called to check if they were hiring. I had a lot of time to study software engineering on my own, but with a little luck, I also learned the power of personal connections at building your career. Through a former co-worker of my mother’s from two decades earlier, I was able to talk to someone with the power to hire. I told them, “I will work for free for a month, and you will be so impressed with my work, you’ll have to hire me.” …And they did.
This first job I acquired after college was building applications and data synchronization conduits for various mobile platforms. This was a great field, not only because it required very careful use of system resources, but because hand-held devices were about to see explosive growth, which continues to this day. Connections at this job got me into Palm, where I developed an OOP framework for the mail application (and eventually other PIM applications). Connections from Palm later got me into RIM (the BlackBerry company), where I did the same kind of work, as well as back-end work for Text-to-Speech and the BlackBerry Playbook PIM data connections.
It’s been a long road, but I have been a system-level software engineer for many years now. I got my start between Palm and RIM at a start-up called IntelliVid, which did video analytics. There I worked very closely with someone that knew the guts of things like pthreads inside and out. It was a place where people challenged each other to “prove it” when one made assertions. Later, when VMware came calling, I jumped at the opportunity. I learn so much every day, trying to prove it, and helping people (that are already smart) with things that I know. At VMware, I’ve worked on the SRM disaster recovery solution, and have made my way down in the software stack to the I/O path with data replication. I’ve had the opportunity to work on anything from system software to C++ coding standards, and everything in between.
I can’t wait to see what will happen next!
Thanks for asking. I have a lot of interests, probably because I’m an only child, so I try to keep myself occupied. Stuff like…
If you have made it this far, I want to say thanks for stopping by, and thanks for taking the time to learn all about me!
Home of M. Bisson - About Matt Bisson - About Matt Bisson - About Matt Bisson - About Matt Bisson - About Matt Bisson - About Matt Bisson - About Matt Bisson - About Matt Bisson - About Matt Bisson - About Matt Bisson - About Matt Bisson - About Matt Bisson - About Matt Bisson - About Matt Bisson - About Matt Bisson - About Matt Bisson - About Matt Bisson - About Matt Bisson - About Matt Bisson - About Matt Bisson