The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I should start by saying I am not a coder and know nothing about it. I currently work construction. I like my job, and I make a decent living, but construction can be "feast or famine," and layoffs are not uncommon.
Gig work would be an ideal way for me to supplement or replace my income during the slow times. A career in computer science could also be a good transition for me when my body will no longer tolerate the rigors of construction work.
For now though, as I stated above, I am mainly interested in setting myself up to be able to do gig work. Has anyone on here done any gig work? If so, I would love to hear your opinion on it.
I am considering going to school online to earn a degree in some type of computer science. Any opinions about which disciplines are best for the type of work I'm looking to do? Any recommendations for schools? Any I should stay away from? I was searching online, and am thinking [DELETED] may be a good option. Any opinions on that?
Thank you for reading this. I know I have a lot of questions, and I hope I posted this in the appropriate place. Any advice or opinions would be much appreciated!
I am not sure what "gig work" means, "contracting" maybe. However if you want to know what to learn then the best starting point is to look at what jobs are being advertised in your area. For web development C#, ASP.NET, SQL are probably most common. For mobiles Java and Android, or Swift and iOS. For desktop computing maybe C++ and Windows.
There are a number of websites (freelancer.com is one) where that sort of work is advertised. But you may find that clients think they can get a complete website built in an afternoon for less than $10.00.
On demand work that I can do at my convenience when my day job allows.
I think you'll find out that these ideas don't go hand-in-hand with coding. If you want to be good enough at it for others to hand you work, you need to have plenty of dedication--not only learning, but keeping up to date...because this field moves a lot faster than construction.
I am mainly interested in setting myself up to be able to do gig work. Has anyone on here done any gig work?
I don't know for sure what you mean with "gig" work. But anyways..
Member 14550317 wrote:
I am considering going to school online to earn a degree in some type of computer science.
I would postpone that until you are sure what you want. Computer technologies and programming languages have too many options. First search in the net for free tutorials of a couple of languages, look if you like it and if you can understand it. Then choose the one you feel more comfortable with and then start learning in deep / paying for something.
The topic of those IT Camps that promise a lot and are quite expensive have been discussed a couple of times, there is not a big acceptance here in the lounge. But if it is what you want to do...
I would recommend you to get a copy of Visual Studio 2017 community (free for personal use), so you can start playing around. About the languages... C# is a good all-rounder to start with (there are a lot of resources and structured tutorials in the net (one I find OK is C# Tutorial[^])
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
I had a coworker who used to earn a bit on the side helping people configure/etc a well known CMS. IIRC most of the work he did was one off jobs that were only a few hours of work. Something like that seems like it might be a good entry point for what you want to do, being 3-4x off on your estimate is less catastrophic when you're only bidding a nominal 2-4 hours of work, and the small discrete nature of the tasks means it's something you can easily fit in around a second job.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
The best programmers I have ever trained have been from the following backgrounds Engineers, Mechanics or Builders. The people from these professions understand that the end results has to have structure to be built upon. And sometimes it takes more time to build infrastructure than to build the final item.
I have read thru alot of these comments and they all mean well. But, they are kind of discouraging in that they point you in a hundred directions and none at the same time. They best way to start is to start. Getting into a class for any type of programming will help. Anything. Seriously it is all pretty much related. The underlying theories are different for infrastructure. But an If statement is still an If statement. and a logic table is a logic table.
I love working on cars, I love building new things in my woodshop. The things I apply in my job as a programmer are directly related to building a furniture for my wife and daughter. The big difference is when the dresser is done. It is done. When the program is done. Well there are a ton of improvements that someone will think up. LOL.
Enjoy the mental stimulation.
To err is human to really mess up you need a computer
Thank you. I agree, construction is definitely not programming (interestingly enough, I am also a former mechanic), but I fell if I am determined to learn it, I will.
One of the main things that is peaking my intetrest in this field is the amount of contract work that seems to be available. Construction can be very unpredictable, so a 2nd job with a regular schedule just wouldn't really fit me.
Ideally I would like to start doing small contracted programming jobs, as was mentioned above while still working construction to supplement my income and learn about the programming world. Then, in the event of a layoff, I could transition to programming full time.
It's a little overwhelming trying to figure out where to start, but, as you pointed out, the best way is just to start.
You could try the golang tutorial for starters, it is very short and goes through the basics quickly. I would not suggest starting with a programming environment that is going to auto-complete and suggest everything you need to type.
I honestly can't see the "gig economy" working with programming/development except the freelancer.com web sites and there are quite a few of them around. I believe they would be very tough to break into for a beginner.
You are VERY unlikely to get a contract which will allow you to work when your primary job allows you the time, possibly pro bono work but you will need a goodly amount of experience.
As for setting yourself up for future options then get the latest community edition of Visual Studio, a couple of books on c#, SQL Server and web development and start working through them. Once you have the basics then build a couple of applications based on your interests, I did a dive diary for my son.
Never underestimate the power of human stupidity -
I'm old. I know stuff - JSOP
The software world is overcrowded with people who know all about their tools but nothing about the problems. Lots of these people believe that perfect mastering of some obscure programming trick is of any use (well, in their eyes: essential) to the non-programmer coming with a problem far outside the domain of coding. But your ability to juggle five hammers simultaneously does not prove, or even suggest, that you know how to make me a house covering my needs.
You thoroughly know one skill, one trade. You know work patterns, terminlogy, conventions, written and unwritten rules for how work should be done in your field. That is an enormous strenght - we need people like you in the coding world! Exploit it for whatever it is worth.
Don't plan to turn your back to your profession, sort of starting out with blank sheets, to learn "coding in general" - then you will be no better than all the others with no clue about the problem that they are set to solve.
When you pick up a tool that has been created by people in the trade, truly knowing and understanding the needs, problems and issues of that trade, it gives you a great feeling. I've got a few of those on my PC, such as Steinberg WaveLab for sound editing, or Photoshop. Or for that sake: MS Office for document production. There are reasons for such tools never been knocked out by free open-source alternatives: Those coders never analyzed and understood issues and requirements, they just tried to make something roughly similar to the successful solution. Copying a solution only vaguely teaches you what the problem was.
Coders are experts at solutions for coding problems. They know and understand compiler related issues, requirements for a VCS, how to automate system builds. So they make good tools and solutions for themselves. That does not guarantee that they will make good solutions for completely different problems.
So, hold onto your skills when you move into the software world. You can probably make most use of them in design and program architecture phase, rather than in the nitty-gritty coding phase. Which means that you should probably not aim to be a one-man company, an independent consultant solving any sort of problems you don't understand; you shold rahter train yourself to move into companies where you will be the problems and solutions expert in your trade.
I was teaching general programming for a number of years. Every know and then we had students who had been working for years as unskilled workers, on-work training only. But they knew how this knowledge was to be used, applied! They asked all the good questions, pointed out which alternatives were suitable in which contexts, they supplied (and sometimes corrected) the textbook on established terminology etc. etc. They were worth their weitght in gold!
That is the kind of designer/architect/coder you should aim to be. A domain expert. One who knows how the real world really is, in your part of the real world.
Can you be your own salesperson? That's going to be a big factor.
Also, unlike construction, if you're looking for remote gigs online you will be competing with people who live in countries with a very low cost of living.
A lot of IT people I know recommend young people go into the trades if they have any aptitude for it, rather than computer work. One guy I work with is studying to become a nurse. And the company I work for is hiring every skilled welder they can find- hundreds. The number of IT workers they've hired in the last 5 years can be counted on one hand with fingers to spare.
*Any* industry that says there's a big shortage of "x-workers" is really saying they want cheap labor, and need an oversupply to keep wages down. And the schools profit from painting a rosy picture.
A career in computer science could also be a good transition for me when my body will no longer tolerate the rigors of construction work.
Talk to older computer workers about how easy it is to find work. They've got a younger 'expiration date' than you do.
Find out if coding really suits you first- take some free non-trivial courses on Coursera or something similar. That will get you much further in your decision-making process.
I started with C in University. If I was teaching now, I'd start with C# move to C++ then to C. Then and only then would I move lower to .NET, IL and maybe a little on assembly to help them get a better idea of what is going on under the hood.
The idea is to move on to the "candy" languages after you fully understand pointers.
The idea is to master "pointers", get a feel for some of the most difficult concepts early.
When I went to school the professors were very strict when they taught statics and dynamics for the engineers; the idea was to separate the "wheat from the chaff", early in the program. For example, my younger brother said he got a "D" on his first 4 week exam, because he forgot the -> vector symbols on his equations, even though every answer was correct with all the work shown.
The idea is to let the student determine if the subject matter is right for them very early on, so they don't make too much of an investment and bail later than they could have.
Pointers are not something I would teach to a beginner, you can screw up your code so easily and make it so hard to debug that way.
These days, a lot of companies cannot get programmers. So the concept of weeding out the lousy students is old-fashioned and should be deprecated. Modern teaching methods can help weaker students become as good as the strong starters, by the end.
All programming languages have strengths and weaknesses, if you study computer science in a University, you will probably have used 7 or 8 languages by the end of it so it will be second nature at that point to pick up a language and start using it fairly quickly.
Last Visit: 31-Dec-99 18:00 Last Update: 21-Apr-21 13:20