Honestly, I just wanted to see what the hype was all about, then see if I could do it. I got a C++ book from a friend and initially looking at the book I ran the other direction. I was in my second year in college then. Then about my third yr in college I decided I would go for change my degree from CIS to B.S Software Engineering. Really to see if I could do it at first, I thought if I could this would streamline me into project management or something of that nature since I wanted to be in tech but not a dev.. Well after taking a few courses in C, javascript, I took Java and I sucked at it at first. Then something weird happen in my Advanced Java 2 class, I got code high one day.(I was working on a calculation project). This lead to a ever-ending search for that feeling over and over again... So I ended up taking the rest of my OO classes including VB and C++ and I decided code high was the coolest thing in the world.. So I decided I would pursue "code high" as career which is dev.. Now I code for a living and I am addicted to dev and sys stuff... I'm that which I said I would never be!! Honestly I just love building things and breaking things...and building them again.
HN user
jester5
a dev..
lol..
Thanks for the feedback Maxdemarzi.. Your right I think it just gets frustrating when I'm starring into the eternal sea of abstraction not knowing if the bug is somewhere in session manager, datalayer, or hate to say it sometimes UI..The someone comes along and says it over here in xxx after looking at it for minutes.. but.. You are right though I can not compare myself to them....
Actually, I would go for it. I think with your experience the University of Illinois would be more than enough.. Crap.. A degree from University of Phoenix would make you CIO with that knowledge.. I'm not trying to hype you up but honestly with you experience any degree should work..
If you could some how port all that knowledge to "right cerebral hemisphere" I would flat out give you my degree..
I see where your going with this and you are right. In any of these scenarios there are no central controllers identified. At the same time these do not deal with identifiable traits the display a signature of an "originator". For instance with the antennas, there was still an initial program/programmer that designed the program that would carry out instruction to design antennas. With the ants we are still not dealing with the how did ants get here? Why do ants have such a variety of complex and unique genetic structure design?
http://www.ncbi.nlm.nih.gov/pmc/articles/PMC1208186/
I was a late bloomer and did not start programming until 28 yrs which was through my degree program in BS Software Engineering. I had taken js. java, sql and really did not fully enjoy it. It was not until I had taken VB.net in my senior year where I changed. I had a project that I was working on that performed financial calculations. One day I started a new version of the application and literally started at 7:00am and did not eat or move until 8:00pm that night.(I think I went to the restroom and drank water, can't remember) I had code high and ever since then I have been in love with programming now I'm 34 and a .Net Developer for a mid-siz company.
now playing fallout 3 lol....
thanks for the advice.. I watched it and I bought it and works great..
It sounds like to me you are doing everything right. I think studying interview questions is really good. Some possible interview question might be;
1)Describe an algorythm? Then describe it within it's implementation.
2)Write a function with two parameters that returns a string in a reverse fashion.
3) Write a SQL queries? Use inner, outer, and all other joins when needed depending on interview requirement of the question.
3)Describe dependency injection?
I think for the most part interview question's can either can go one way or another. They will either slam you with conceptual CS stuff or actually have you write code. I would look at as many question's as possible. Then I would literally ingrain the basics of coding(In order to implement anything they ask you in the interview on the spot). Things like loops, structures, stacks, recursion, and everything else. Learn them and understand how to implement them at their most basic level.
Let them know that you are addicted to programming and learning new technologies.
Also get involved in as much open source projects you can handle.
Focus on the fact that you understand business process and how that relates to software dev.
Mock up some demo stuff or have a site that contains your portfolio. (Have demo of something cool for each language you know.) Take you laptop to the interview and show them your work and explain the abstraction and logic.
Focus on any projects you have done in the interview even if you did not get paid for them.
Find a solid mentor that has been in the industry for 10 plus years.. learn everything from them.
Put them as a reference.
Really nice one guys! I'm not a entrepreneur yet but I am a Software Engineer and a recent College Grad. At the same time I'm in the process of discussing a new Hacker Space Venture with other Black Software Engineer. So you now know three black tech's in which one is not as successful as the first two nor an entrepreneur but a successful engineer and on the rise.....
Actually... You talk to much! lol
lol.. that is funny.. So true though..
Honestly, This is going to sound slightly mean and unrealistic but I think it would work. I would have them start with Assembly and then dabble with C++. At 12 years old they can dedicate lots of time the concepts. Yeah they might not be deving anything cool right away but it the long run they will be amazing.. So I suggest Assembly, Visual C++ using Visual Studio.