Skip to main content

Goals for next three years

I have decided that if I can accomplish one of the following things within the next three years, I have done something special:
- Author a whitepaper
- Start an open-source project with other contributors
- Speak at a (somewhat important) conference on software

I plan to accomplish this by doing a few different things:
- Read and write a lot of code!
- Read and study online and printed software novels, particularly the Head-First, Fowler, or O'Reilly series of materials
- Subscribe and receive emails of tech articles (I already subscribe to TechRepublic)
- Active use of Twitter and Linkedin
- Making use of software community message boards

Of course, additional suggestions/comments are all welcome.

Comments

  1. I'm wondering why you want to start an open-source project. Would being an early member of a project team be close enough? I'm sure there is at least one project out there that would tickle your fancy.

    ReplyDelete
  2. A fledgling project seems intriguing. If you have any, let me know. This is mainly to allow me to apply my effort to something potentially useful in industry.

    I was also thinking of something like working to enhance NS2 (http://www.isi.edu/nsnam/ns/) or NS3 (http://www.nsnam.org/), but an early project wouldn't be bad also.

    ReplyDelete

Post a Comment

Popular posts from this blog

Software Design Principles - SOLID

The SOLID software design principles weren't called SOLID while I was in grad school, but the concepts were there in my Object Oriented Design course. They're worth mentioning here, primarily because I think once you start coding and become dangerous, it's one of the best ways to stay organized once you incorporate it into your daily coding routines, and it even changes your way of thinking for the better: https://en.wikipedia.org/wiki/SOLID

Best Documentation of a Free Software Package

One oft overlooked artifact in software development is the documentation. An API that is not well documented is no API at all when time is of the essence. That's why I think it is important to discuss some of the tools I have used and their documentation. AutoIt - I love how you simply press F1 within the AutoIt editor and boom, the reference to the particular syntax or function pops up in the help window. This help file is well written, self-contained, and chock full of examples that can be opened up in the editor right from the help, a fantastic symbiotic relationship. After installing AutoIt and giving it a try using their examples, I was able to create client/server scripts, GUI scripts, and window management scripts in no time. Overall, AutoIt is tops in this competition. A+ MySQL - At the bottom of each page of documentation that discusses a particular statement, users are able to post comments containing code snippets for that particular statement. This is great..

Fun with MySQL + PHP

Lately, I've been getting a lot of requests to build websites driven by lots of data, so I've been reading heavily into MySQL and PHP. I've been relying "Beginning PHP and MySQL: From Novice to Professional, Third Edition" by W. Jason Gilmore. I was concerned with his use of connecting to MySQL with a plaintext user name and password, so I went through a few tutorials online: [hvassing.com] [studiolounge.net] and the SQL reference manual: [dev.mysql.com] Of course, they did the same thing. I'm working on trying to implement an SSL solution to login, but unfortunately I think it'll require an X.509 certificate.