A Career in Programming which way to go!

[Lost User]

First piece of advice: take a good look at the industry and take note of the technologies/languages/frameworks that are 1) popular, 2) used widely in the industry, 3) pay a decent salary, and 4) available within a commutable distance. Big companies tend to need a degree (or relevant experience) but smaller companies are always looking for people. .NET and Java are very popular and we're bringing in developers from all over the world to fill vacancies. Neither technologies are going away any time soon either. Niche (and usually more interesting stuff) is fun, but you'll find yourself wondering if you're going to have a job next week all the time. The pay can either be astronomical (rarely) or bottom of the barrel. Whatever you get into keep your skills current. Nobody codes perfectly, there's always room to learn and improve. I got my first software job (without a degree) by going to an interview with reams of my own printed out code and demos of what I could do. Don't be afraid to take a risk :)

Ah, I see you have the machine that goes ping. This is my favorite. You see we lease it back from the company we sold it to and that way it comes under the monthly current budget and not the capital account.

[B4DG3R]

Sounds like good advice thank you!!

[B4DG3R]

I am currently working but my full time job is a world away from software development I'm a service engineer working in horticulture! The HNC/HND part time then possible degree route is what I think I may do it's just trying to get some real world experience in between as at the moment I can't afford to quit my job as I have a family to support !!

[Gary Wheeler]

<GrumpyOldGrammarNazi> First piece of advice: don't end every sentence with an explanation point (!). It makes you sound manic. </GrumpyOldGrammarNazi>

Software Zen: delete this;

[W Balboos GHB]

Some food for thought: Many of the best developers around (even on CP) - perhaps the best - never took a course in programming. It's just something they did and somehow managed to make a living doing it. Getting in - that first IT job - is the tough one. As I usually put it: 25yrs old with 30yrs experience. That being said, in that job, you'll need to carve out just what is it you do. Myself? I'll freely admit they could get a better coder than I with far more knowledge in all the various allied technologies. Why me? Because I can solve problems faster and better than any of them. And intuition. Those are things you really can't learn. You may have a different attribute to present. What can you bring to the table? You may not know, yet. A small productive group needs multiple skills. In school or out, I presume your coding already because you can't help but do it. Discover what you're good at. Discover what you like to do. If you're really lucky, you can bet paid for doing them both.

Ravings en masse^

"The difference between genius and stupidity is that genius has its limits." - Albert Einstein

"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010

[PIEBALDconsult]

You have already lost.

[B4DG3R]

Point taken 👍 And thanks

[B4DG3R]

If I hadent asked I would be loosing. My asking is me carving out possible paths for me to follow. Hence pushing forward and not loosing! But thanks for the input anyway ;)

[Mark_Wallace]

In programming, the only way to go is recursive. .evisrucer si og ot yaw ylno eht ,gnimmargorp nI

I wanna be a eunuchs developer! Pass me a bread knife!

[B4DG3R]

I like it! Thanks

[B4DG3R]

Thanks! That sounds ideal and I think if I were younger it may be a great way to go, not that I'm old but I'm at an age where I think I may get only one chance to retrain to this scale. Which is why I feel I need some actual qualifications + a decent portfolio under me to stand a good chance of getting a starting point!

[KBZX5000]

I recommend getting a grasp on the industry first by doing an entry level job. At 28 your odds seem better if you start by imitating people with more experience. Going from "writing code" to "creating something with monetary value" requires some understanding of how to deliver work in general. You can build a portfolio, but chances are high it's going to be too narrow in scope to be of any use. As an example: good portfolio's (in my professional opinion) show that you can tackle complex problems and solve them in a maintainable way. In practical terms, this means doing something that covers multiple languages (let's say python and C#), independently figure out who's prior work to combine (with proper references / attention to licenses!) to produce "a stable result" of some kind. And you would need to generate some kind of validation that shows your approach is valid / predictable. Full test coverage is probably the easiest way to go about that. The catch is, that none of this is particularly easy without a frame of context on how you should present all of this. If you botch up the presentation, most people (= management) will simply fail to understand what you did, rendering the entire thing moot. So.. this leaves you with trying to get a entry level job, so you can start figuring out how to report work in an a manner both management and fellow developers will understand. After about 3-5 years doing that, you can probably build a decent portfolio and get a better job. In my experiences, the industry is still very much build around "trail and error". A lot of people seem clueless. Some are full of shit. Others visit CodeProject and are alright I guess.

[B4DG3R]

Thanks sounds sensible to be fair! I didn't ever expect to walk into a senior developers job just because I'm older. Starting from the ground up was always where I expected to be but I think my aim was to try and gain a substantial qualification first giving me enough knowledge to gain a better paid entry level job so I didn't have to take as much of a pay drop! There are quite a few training jobs local but they are apprentiships less than minimum wage and as much as I would love to jack my job and go for it I can't afford to take that pay drop! Which is why I wanted to try and do my HNC HND first then possibly my degree if time/situation allows! Do you think I would be better off doing this than going straight into an entry job with no quals? A lot of the better paid entry jobs require a BS in Computer Science and the better paid jobs at big company's. Does the industry view experience better than quals? Or is it all down to the company?

[robdocobo]

As an employer and programmer with 30+ years experience, I think it is worth considering the following (from my perspective): 1) On the whole, employers want a balance of people who are very productive with specific technologies (which requires time and experience) and those who have natural programming skills, that is a mix of being able to think logically, some degree of numerate competency and able to solve new problems; (you either have these skills or don't). 2) Today, the software development landscape is rapidly evolving with new technologies / approaches appearing continuously. Hence, it is wise to place for a career of on-going professional development and being willing to adapt and take on new things. This is a personality trait, that is possible for some to develop if they do not have it. 3) There are some common threads and generic aspects of best practice (e.g. software life cycle, revision control concepts, issue management, testing strategies, release engineering etc. which you will need to be a good programmer. Taking the above together, I would suggest aiming to fine a junior role / internship where you can gain experience of 3 from a mentor and that gives you the opportunity to use current in-fashion programming technologies. Assuming you have the natural programming skills from 1, this will allow you to become productive in something employers will find valuable. Then as your move one, seek opportunities that provide opportunity for development as in point 2, or better still in the role you are in at any time, track developments and where appropriate evolve what you do to use them.

[Ygnaiih]

Python is in demand. I have no idea why. See if you can write a new app in Python without looking at the book. Set a task for yourself that requires logic to solve. I have 12 programming languages and use 5 of those right now. It is not easy getting into programming and luck and skill are both needed. My son got a go no where job right after a two year degree and more than doubled his salary with another company after a year. That was luck and skill.

Leadership equals wrecked ship. If you think you are leading my look behind you. You are alone. If you think I am leading you, You are lost.

[JackPeacock]

Not sure what it's like in the UK but in the US it's difficult to get a good developer job without a degree. Those ads that say degree or 5 years? Don't believe it, they aren't treated the same. 5 years experience means any technical degree is okay, not just a CS degree, but when it comes to interviews the ones without degrees go to the bottom. Yes, still a chance but only if the top of the pile are too expensive or fail the interview. As someone who's been on both sides of the interview table I do agree with most of the points above. Experience counts, especially in senior positions. Junior positions it's less of a factor, so the only tangible data to go on is...degree and subjects in school. Bootcamps? Anyone who's been a programmer for some time knows you can't really learn to be a commercial developer in 12 weeks. Maybe, maybe an entry level position where the company expects to train for the job. Expect pay grade to be competitive with janitorial services. When you get to positions that ask for 10+ years experience degrees don't count for much as long as you have one in a technical field, unless it's a Ph.D. Problem with Ph.Ds is too much focus on academics, not enough on how to build code in an economical and profitable way. Good for a research position, not so much for engineering the deliverables. There are other aspects to development work besides coding. What makes a prospect stand out are the communications skills. Can you explain your work in a way others understand? You'll be on a team; they have to know what you are doing. Some day there will be "the next guy" working on your code, will they be able to follow your logic? Do you even comment your code? If you say "the code is self documenting" in an interview you might as well stand up and leave. Managers who have to worry about continuity and maintenance know first-hand that particular cliche is a myth. Consider some classes on writing, an articulate and well-written report or manual will demonstrate you are more than just a code monkey.

[AmidstTheRuins]

You won't want to work for every company anyway - some places will have developers who will try and hand hold you because you are new. They will try to restrict you and have a go if you don't do something there way. These people are usually stuck in their own rut and you can go way past them within a year or two. Don't show too much respect to these "Gurus". They are the sort of people who will deliberate for months over upgrading to a new IDE or worry about upgrading from Win 7 to Win 10. Just download the latest newest version and get on with it. Setup VMs and have both. Set up your own servers and test environments so you can try stuff out. Jump in at the deep end and with a few years experience you will move past these people. It is good to have a mentor but you can achieve a similar thing watching videos online. In a work or apprenticeship environment it can be very slow and sometimes patronising especially if you're already pretty senior in your current role. Don't throw away what you know from your current job - try and write some software that uses your expertise in this area as the domain subject whilst learning the development platform. Pick an area and get good enough at it to get hired. e.g. .NET Desktop apps .NET Web apps Webforms,.NET Web Apps MVC, Java web apps, Python web apps. In other words pick a set of tools (IDE, database) and build things with them. The .NET environment tooling is different from the Java environment despite both being application programming languages. Same can be said for front end web dev or even developing on a different platform e.g. if you use Windows, Mac or Linux. Don't try and learn loads of different platforms to begin with as when you get a job it is likely the main project you are working in will be a single platform. You can learn lots of other platforms once you are hired. Once you have a job after a year you will be able to apply for other jobs such is the demand in the UK. Also you end up repeating yourself which is pointless, for example i'm doing a uni course where I am learning Python and using it to parse HTML and XML. I already have 5+ years experience with C# and .NET so I could do it much quicker with this. I'm not sure I need to know another language currently to perform this task (using Python as it's required for the course). Although learning more than one language is a great thing to do, it's something to do after you have published with your first language. Be willing to apply for jobs outside of a 20 mile radi

[tom1443]

My only advice is that learning the "how" of programming is relatively easy. In fact it's expected that you be able to pick up a new language, IDE, VCS, framework etc. on your own pretty quick. But in my opinion what separates the men from the boys and allows you to go further faster in a software career (if you want to stay technical and not be a manager) is a strong theoretical background. And I think the "why" can be harder to learn on your own. For this reason I don't think I would recommend boot camps to someone who already can program a bit.

[rubinstu]

I am sympathetic to your cause. Being in the USA we have different terms for degrees, course tracks, etc., so I may not understand the details of your situation 100%. That said, here are some thoughts: 1. You are PLENTY young enough to retrain at any level. There will be some sacrifices, but they will be short term. 2. Focus on skills that are not easily commoditized. Python is great, but it's a tool that is easily learned, and is often used to create "throwaway" code for testing, utilities, etc. It's not really the basis for value-add on major projects. A fundamental understanding of computer science concepts will last your whole career and is not easily outsourced. 3. At least in the USA, bootcamps are quickly earning bad reputations. They teach the tools, not the fundamentals (which would really be impossible in such a short timeframe). Their hiring numbers are generally recognized to be suspect. 4. Unless you have serious personal commitments (like kids), I say dump your day job, and get yourself a genuine 4-year degree in Computer Science, Engineering, or something that will last for years. Borrow, skimp, starve, to do whatever it takes to pay for it. Good luck!

[C0byC]

You mentioned that you are working in horticulture. That's flowers right? ;P I would suggest look at your current situation, what can you see as a 'real world' problem within what you are familiar with. People love to collect and retrieve information, for example, if you are still writing things on paper, create a simple but small application (web page, console app, whatever) that makes collecting that information easier. It is much easier to apply ideas to what you are familiar with, it doesn't matter if there are 10000 applications/systems that does what you want to do, just start with something that you can associate with to make your problem solving and learning easier. After all programming is not writing squiggly packets or text, it's finding a solution to a problem. People using your application/website/system aren't interested in if it was written in .Net, Java, Python, Ruby, C++ or any of the 1000+ programming languages available today, they want something that makes their life easier. You mentioned you are learning Python, great! I started with plain old Turbo Pascal, then C, then VB, then C#, VB.net, Ruby, Pythion.... javascript...etc.. and so on.. :wtf: The point is there is no real answer to "Which way to go" or what programming language to pick, they do have their different uses, but for the most part they do the same thing. (if, else, when, for, foreach, a=b+c etc..) You are also guaranteed that you will learn more then one way of doing things, you will learn how to collect data, save data, retrieve data and present data, all in different languages. :-D Look at what you think is a problem, try and make life easier using whatever language you find more rewarding. Once you can show something to a prospective employee where you took a simple idea and turned it into a simple solution it almost carries more weight than having 10 diplomas or degrees and no work to show for it! Happy learning and happy coding! :)

Over..