Thank you both for replying. I dont want to waste 4 years into college to get into debt, however I am thinking of CC and working on projects while I do that, or maybe working the entry level. If I were to work entry level and work up, what are the chances that jobs in this field wont accept me without a degree?
100% agree with everything here.
Absolutely. Every man is usually really good at one thing, but utter dogshit in everything else. Half of my team can only code and click "run" in JetBrains or Visual Studio. They don't know how to actually compile anything on the command line, or handle deployment scripts / container use to AWS. I'm like 15 years younger than these people too and they're fucking incompetent.
Low. Some companies will want a degree no matter what, and you just have to accept that. However, once you get that first job (the one you're in @ $13/hour), you're in for the most part. The next job you go to won't even care about that, they'll want to ask what work you did at your previous company, skills/values that you possess and your ability to work in a team. Kinda like a SAT score, they stop caring after your first job. It's literally the same thing, but in the professional world.
So there are three things about high asking prices
If your one skill is writing APIs there is a ton of opportunity for you. The need for young developers to repeat the pattern established by seniors/architects is crazy. Plus the young developers get to memorize good code as they learn.
If you can solve your own problems, or come to the team with what you've already tried, and be respectful of their time you will go a lot farther. It's only when I'm repeatedly explaining the same thing that i get annoyed.
Agreed.
These places are usually terrible work environments. There is a lot of arrogance and a lack of collaboration at these places.
Starting out with a junior web developer job on your resume at such a young age (when you would be in college) will stand out in a stack of resumes that mostly look the same in my opinion. You might get interviews just because they're curious. I would advance that resume if the github was decent code.
If they're trying to recruit autistic studyasians, this is a good way to do it. I don't know why you'd want any on your team, much less a full team of them.
I got the questions right but only because I'd done the problems recently and had my solutions on hand. One of them was a fairly involved dynamic programming question and I barely had time to type it in in the 4 minutes, much less solve it.
Not being a turbo autist helps too. I was chatting with the head IT guy at lunch earlier today and we finally found someone for our data analyst position and they don't have a degree. The SQL you needed to know during the technical interview was not hard.
tbh I struggled to write complex SQL until I started actually working problems in it. The main issue for a dev is that your default approach is usually going to be interacting with the database as little as possible and doing all your data massaging in the programming language you're writing your application in. For most developers, the extent of your practical SQL knowledge is going to be SELECT, INSERT INTO, and maybe some JOINs.
Don't forget DELETE FROM. That's about the extent for many developers, more so new devs.
Too many "architects" going overboard reading medium articles and not considering business practicality.
Agree.
Honestly with the way development is trending developers don't need to. Data Engineers handle the SQL and data achitecture and do it well, and developers copy the data to code models with an ORM and go from there.
You won't find work anyway unless you live, breathe and eat code
Oh I absolutely agree. I'm more just talking about the general tendency of developers to claim to know SQL in order to tick a box on some HR-drone's form in order to get a foot in the door. For some reason, jobs still expect you to claim proficiency in SQL despite few developers ever really interacting with it.
To be fair I think that's often clueless recruiters who have no idea what a developer does and are filtering by buzzword.
Fair point. What I was thinking of as a start was a project like an rpg game and something related to an app/website. I do digital art as well, and I'm fairly good at graphic design, at my old job my old boss even asked me to make a graduation certificate for the youth program, because I was fairly competent enough when I did posters and whatnot for the program. I try to code at least 1 hour/2 hours everyday, just for a slow steady practice, so I am planning on getting into more steady works and more heavy coding eventually.
This is a programming thread. Execution time is as important or more important than mathematical precision in a great many applications. Arguing for perfect mathematical implementations makes a lot of sense if you are doing stress calculations for a finite element model of solid structures, but it makes no sense at all if you're calculating the size of a small GUI element in an array of pixels. Truncating 22/7 down to 3 significant figures is great in that case- the code will be faster and the loss of precision will always be sub-pixel.Arguing about this is like arguing that 22/7 should equal(3.14....).
That's not even what happened though. He was arguing for rewriting mathematics itself because he's too autistic to follow even the pedantic autism of mathematical logic. In fact the only thing we all agreed with him about was that his interpretation of modulo arithmetic was the one that actually has more use in practice. If he'd left the argument at that instead of going off the rails into crankery, then he wouldn't have to suck cold Ls now.
It's unfortunate that this is true, however if you don't work as a developer, go home and work on projects, constantly exploring new technologies in your spare time, you won't really get out of the cycle of being treated as just another code monkey.
