Hitting a Wall

+1 I agree that front-end developers are sorely lacking. Currently, if you know AngularJS + Bootstrap then you are a hot commodity. If you combine AngularJS + Bootstrap + NodeJS then you can probably name your own price.

I agree that most of the time the solution to a problem is not really a math one. I just used that one as a simple example of where the obvious answer isn’t even remotely close to the best one because it is one that I have come across recently - with respect to JavaScript homework questions misteaching how to write JavaScript. The way the question was worded implied that it related to teaching how to write loops where it would be obvious to any reasonable programmer that the problem could be more efficiently solved without a loop. In this case the art of problem solving is the simple recognition that there is a solution that involves the end point values without needing a loop. Having determined that actually working out or looking up the details of the solution is trivial.

The point I was attempting to make (obviously unsucessfully given the response) is that a good developer/programmer can visualise relationships in the requirements that can provide relatively simple solutions. They can then backfill code to solve the problem that is much shorter and more efficient than that used by others who have simply taken a brute force approach to solving the problem.

The best programmers posess the talent of being able to visualise patterns in the data that lead to solutions to problems without having to apply a brute force approach. Most programmers can’t do this and so end up writing far more code than is necessary.

Totally agree, I’ve been in these types of interviews too - it only shows me the company isn’t a good fit for me rather than the other way around.
One other exception where maths is used heavily is in graphics.

When I build things I do tend to make them more complex than they need to be. Though that is only because experience has taught me to anticipate new features. Anticipating possible features in the beginning and using a solution that would make it easier to add those features. I’ve never worked at a place where I’ve completed something and never seen it again. High consideration for constant change is a high priority of mine based on the environments I have worked in. I also will say that “complexity” us merely an individuals interpretation. What would be complex to one person might not be complex to another. When I get handed something I didn’t build I always believe initially it is “complex”. So to each their own.

I agree. Nothing you said there contradicts anything I said. You are talking about complexity in terms of allowing for additional functionality where my comment relates to dramatic differences in complexity for identical results.

To start I’d recommend learning html5 and css3. Start with the basics. Start working with some templates to get familiar with working with code. Then look into learning how to use wordpress, there are plenty of online tutorials on how to install wordpress onto a server, and after you know how to do that working with wordpress is a relative breeze. Wordpress is a great way to ease into working with PHP.

I develop with WAMP then upload my projects when they are finished.

Remember to take it slow, one step at a time and only handle one new thing at a time. It’s important to not get overwhelmed, because there is a lot to learn.