I've been programming professionally for a couple decades now. I've always run my own backups until recently so I never had a need for a centralized repository like git until last year.

Rather than a flow chart I'd suggest a decent tutorial. Branching is the main reason Git is so popular and most everything you need to learn is probably in this one tutorial.

https://learngitbranching.js.org/

Good Luck.

Those tables are not correct either. There should be rows and they should not be nested in that way. Also the H1 tag should not be where it is.

Seconded. I have been working as a programmer for 20 years (was literally my after school job in high school). I went to college long enough to realize they were a good 5 years behind the industry when it came to technology.

If you passed the companies entry interview you should be fine. Just pay close attention and learn as much as you can for the first few months, after that you can probably coast comfortably.

Business owners in the tech world also seem to be colossal faggots so they do okay.

Too much jpeg to read the code.

Mix in projects you want to work on. Programming is easy to burn out on when you only write code for others.

Developers have forgotten how to develop great programs

Don't blame the developers. I have been programming for about 20 years, and the problem is with the demands of management. Most developers I have worked with only develop bad code because of time constraints and other processes put in place by their managers. Most of them are as disgusted by it, if not more-so than you.

There's still a niche there of now, but there are less and less mainframe systems being maintained these days. Everyone is moving to modern hardware architecture.

Mainframe development is defiantly an acceptable answer. Good luck.

Can I ask, why do you want to learn cobol? I mean I don't have anything against it, but there are a lot of languages out there, and cobol isn't exactly cutting edge.

Sometimes open source and corporate interests do align. If a corporation wants to have a large pool of potential engineers to hire from, they need a large base of programmers with experience programming using their platforms. Why else would Google released their AI Engine TensorFlow? Other recent examples include Microsoft Open Sourcing the .NET platform and Apple opening up the Swift language.

Spoiler Alert. It typically ends with a botnet.

Bug bounty programs are typically offered to people who are exploiting servers, not just finding exploits in desktop software. Either way, considering the time it normally takes to do that kind of work, bug bounty programs don't often pay that well.

As for the servers they were not interactive at all. There probably would have been some limited interaction if I had downloaded the file it was calling and attempted to reverse engineer that, but I really wasn't interested enough to take it that far.

The last time I took the time to reverse engineer a virus it was because it was written in VBScript. I found that fascinating because that is an interpreted language and not compiled code. I wanted to know what it was the programmer was attempting to exploit on the target machine. The scope of his potential victims was limited to windows computers, but depending on the exploit the virus may have been even more targeted than that. As it turs out it was more limited to that, the virus was targeting Microsoft Office's ActiveX components. Most windows computers had those files regardless of whether or not MS Office was installed, but to trigger the exploit either outlook or word needed to be opened. Only people with MS Outllok or MS Word would be affected. As far as what id did, basically it made several calls back to various servers and await a response most likely to install another more advanced virus.

I don't use python a lot personally, but I would highly recommend it to new programmers. It is easy to use, read, and you still accomplish some impressively advanced software with it. There are also libraries that make it so you can write and deploy cross-platform desktop apps (TKinter) and is even a new open source platform for web development (Django) that is getting to be pretty impressive.

Not sure which resources would best suit you because we all learn in our own ways, but if you want to mess with reverse engineering you could download a copy of the linux distro "Kali", install it on it's own partition or thumb drive. It comes with several tools for reverse engineering so between their built in documentation and a little google-fu, you should be able to figure out how that gmail immune virus was supposed to affect your machine.

I've only ever done it with the virus' that are emailed to me. I have also programmed a couple of my own just to see if I could. I never made anything more malicious than a virus that could quickly overload a computers memory by abusing a web browsers ability to process JavaScript code. That would cause a blue screen of death in older versions of windows and force a reboot, but didn't do any permanent damage.

You can start tinkering with reverse engineering inside your first year of programming if you really want to. It's kind of tedious though since decompiled programs have obscure variable names and no comments. That makes the code difficult to read and understand. To make them easier to work with you kind of need to use an editor that can re-factor variable names as you come to understand their purpose. Eventually that makes the code more readable and even usable if you so desire.

I've played with a few just to see what makes them work. For the most part the subject isn't all that interesting to me since I don't get paid for that knowledge the same way I get paid for more commercial programming work.

At that age Objective C is a bit difficult. Maybe start with BASIC, Objective C can wait until after potty training.

That's not just pathetic, it's also a dangerous security risk. My colleague only had problems with SQL joins, and debugging stored procedures.

Same here in the 20 years I have been programming, I have met only one female programmer, and she was just average. One time she spent two days trying to debug a piece of code before asking me for help, and I found the problem in literally 5 minutes.

There are pros and cons of both options, and even some additional options.

If you are concerned with bandwidth, and storage space then you may want to call them from an external source.

If that is not a problem then you may prefer to host them yourself which may be be slightly faster since it does not require a second server be contacted for resources.

Also if you link to them on a third-party server that third party will have an additional data point to track your websites users, which may or may not be an issue depending on your users and content.

Fair enough. I assumed that you were working independently, as it sounds like you are working from a personal machine. If you are looking for some additional income, there are several sites out there. I use freelancer.com, but some of my friends have had good luck posting to their local craigslist, a lot of local businesses like working with someone locally, in case there are problems that need to be addressed in the future.

Since you are working for another entity, I should note that you may want to check your non-compete and non-disclosure agreements to ensure you can do side work without violating those agreements.

If you are already on Ubuntu, why are you still on SQL Server? There are several open source databases that you could be using instead.

Mono would more accurately be described as an open source implementation of C#. I actually have a similar background as OP, and was here to recommend a transition to open source. I learned a lot from the experience, and as Microsoft is now moving to a position that is more friendly with open source (in fact they are even working with the team at Xamarin to improve Mono), it is not a bad idea for OP to position himself as a developer who can port existing code from a Microsoft back-end to an open source back-end.

I preferred Notepad++ when I was on windows, but your comment made me laugh out loud so thanks for that.