(Part 2) Best products from r/webdev

I've posted this stuff before, but hopefully you'll find some of it useful. Also avoid EIG hosting providers like the plague.

First, get a domain:

• I use Google Domains.
  
• Namecheap is also super great.
  
• If you use shared hosting (see below), they often offer included domain names with your purchase.
  
  Second, find hosting:
  
  
• Github Pages offers great static site hosting. Free.
  
• Shared hosting like DreamHost is great if you aren't comfortable managing your own server but want access to databases (they also give you email addresses with webmail access). Costs a monthly fee.
  
• Use a combination of PaaS like Heroku and Firebase. Free (can pay for more features/performance).
  
• Your own VPS (virtual private server) like Digital Ocean lets you configure just about everything if you're okay with system administration. Costs a monthly fee.
  
• Buy a Raspberry Pi and hook it up to your router (assuming your ISP gives you a public IP address). This is essentially setting up your own server. One time cost.
  
  Third, figure out how you want to make the site:
  
  
• Use a CMS like WordPress, BoltCMS, Grav, DjangoCMS, etc...
  
• Use a static site generator like Hugo or Hexo.
  
• Write everything yourself (too many options out there to link, depends on your language/technology preference). This is the route you're going.
  
  Other stuff:
  
  
• You can get free SSL certs for your site (especially important if people are going to be entering information) from Let's Encrypt.
  
• CloudFlare acts as a CDN and IPS/IDS to help protect and optimize your site (they have a free plan).
  
• A good option for students is to grab the Github Student Developer Pack, which includes a bunch of free goodies.
  
  A few more things you can play with:
  
  
• C9 is cool for prototyping and playing around in a VPS playground with a nice built-in editor. It has a free plan, but last I checked it still requires a payment card for verification.
  
• HyperDev is another cool Node-specific playground.
  
• Forestry.io is a new service that gives you CMS-like functionality with Github Pages. I have not used it.
  
• Prose is an editor application for managing Github content.

You've chosen an interesting time to pick up web development! /u/GruntildaJr left an excellent guide on learning front end development, but as a back-end developer I wanted to chime in for the other half.

Learning back-end development without an internet connection will be a little more difficult, but certainly not impossible nor any more effort than a few hours of getting things configured. Nearly any web server can be hosted on your personal machine without an internet connection. Apache is my personal choice and likely one of the easiest to setup on Windows, but Nginx is a lot of fun and there's plenty of options.

Here is a fairly straight forward tutorial for setting up a local development environment on Windows. Although the writer suggests using Zend Eclipse as an editor and I would have to point you towards PHPStorm or Atom with a linter and autocomplete plugin. That said, Eclipse will serve you fine. After completing the tutorial you will have PHP, MySQL, PHPMyAdmin, and Apache set up and running. While not especially fancy, these are the basic tools to start learning the ins and outs of back-end development.

As for learning materials, I love Learning PHP, MySQL, and JavaScript and PHP The Right Way. If you want something very beginner friendly and a bit easier to read, PHP Pandas is a good option.

Of the three, PHP The Right Way will be the biggest challenge. It moves quickly and takes you the furtherest, if you haven't programmed before I wouldn't recommend starting with it but I would recommend going through it after you've gotten some experience under your belt. The O'Reilly book is good for walking through a stack of technologies and outlining how they interact to make a full website, while PHP Pandas is a more thorough dive into the language itself (and it's a lot less painful to slog through if you don't like textbooks). All three are excellent and stand well on their own. If you can only select a single one though, I'd highly recommend the O'Reilly book.

A good companion for any more formal book is the Learn X In Y Minutes PHP Page. It's a little one page cheat sheet to reference when you forget something like the syntax for a switch statement or why you should use double instead of single quotes. There's also a bunch of other languages including JavaScript and I've found them all incredibly helpful. Zeal, as mentioned by GruntildaJr is also a great asset, and it contains the pages for PHP.

There are back-end languages other than PHP along with plenty of frameworks and libraries to explore and learn. I don't want to make it sound as if PHP is your only choice, or the best choice for a back-end language. I do think that it is one of the best choices for a back-end language when you take the learning offline, though. There is a wealth of offline literature, I only linked a few books but the market is simply saturated with PHP texts. The language also stands easily on its own, and for the most part the texts treat it as such. You won't constantly be needing to "pip install" or "npm install" like you do with Python and Node.js.

I hope all of that was of some help, it can be a hump to get over that initial setup but afterwards the learning is much more rewarding. Happy developing and godspeed!

Yeah RoR hosting can be a real pain for your wallet. Which sites/companies have you looked at? And where have you started your RoR learning? I personally love Heroku since it integrates with Git flawlessly, but that's just me. I'm sure there are plenty of other good options out there too. This book is also a great resource to have around, even if you choose not to read it cover to cover.

Anyways, to answer your question: I would spend as much time as possible in a development sandbox on your local machine. Obviously you don't want to be paying those high hosting costs as you're developing and testing the app. Heroku is great because it's stable. I wont repeat everything on their info page since they do a good job of spelling it all out, but if you're expecting some real traffic and want a stable hosting option they are great. Otherwise greengeeks also supports Rails apps, but I've never used them for that; they're more of a general purpose hosting option. I just happened to work on a site hosted there and noticed their support for it. So, if GG really does offer stable support for RoR I'd consider giving them a good look since they're pretty cheap compared to platforms that strictly support RoR. In the end if you do decide to just go ahead and use this a "version 1" learning experience, its gonna be pretty damn expensive. If I were you I'd start your whole web development journey out by learning PHP and MySQL first, but that's probably just because that's the route I actually took...

If your group has already started with RoR and has settled on that approach then I suppose your hands are tied anyways though.

Hope that helps.

I'm going to assume you're a complete newbie. I'm only a few steps ahead of you, really, but I can share some advice. I've always felt like 75% of the battle is figuring out what to learn when it comes to scripting or computer languages in general. And a lot of time, even cutting edge, comprehensive sources are outdated within a few years and, if you follow their advice, you may expose yourself to security concerns. Like leapyquacky said, the question is a bit vague, but I'm going to assume you want employees to access a page with user-specific credentials so no employee can impersonate another, etc:

1. PDOs/prepared statements are the best way to connect to the DB. The PDO documentation will help immensely. It should be easy enough if you've ever done any OOP. The reason for this -- and this is really paramount, especially if it's on the internet -- is the risk of SQL injections.
   
   
2. To maintain any semblance of security, you'd need to hash your users' passwords, and likely with something a little more secure than MD5. There's an excellent article on Openwall about this. You'd need a hash, a salt, and minimum length/complexity requirements for your passwords. This is just not good practice, it's essential if you store anything sensitive.
   
   
3. You'd be using sessions to maintain state across your pages. The best videos I can think of on sessions are behind a paywall, but the documentation should get you pretty far. phpacedemy on YouTube has a few videos on sessions, if I recall. Just remember, if you're using YouTube to learn about sessions, a lot of those videos are dated and the security practices won't be ideal. If you see them connecting to their DB using mysql_connect, this is the case. Listen to the session advice, but don't use that function unless you care to get pretty technical about escaping user input.
   
   
4. You're going to need levels of access on the page -- admin, general, etc., so you can protect information and actions that need to be secure. You'd probably also want a running log of all the changes your users made to the database.
   
   
5. None of this stuff will make much sense unless you're familiar with PHP. The documentation is great, but I recommend reading a good book on it, bearing in mind that whatever you read could be out of date. (Hint: Argh, matey, thar be a website that may get yeh the book yeh want withou' yer payin'.)
   
   It's not hard but it requires a scattershot of understanding that may take a little while to really get. I know it did for me, anyway. Once you have that going on, you'll probably have more specific questions. Lookin' forward to it.
   

In that case here you go.

____


They're ok. Try this. Codecademy isn't bad. It won't teach you much in the way of doing things but it does teach you the way to type out code, the general process and stuff. I can't speak for myself because I work as a professional developer and have been tinkering with code for 10 years now, but I did give the first lesson to one of my brothers. He's not great with computers or the Internet, but he was able to follow the first two sections of the basic HTML/CSS course and able to make his own site albeit very basic in nature nearly a month later (3 week gap following him doing the lessons). He was able to do a rough basic site of his Facebook profile, and he nailed it. It should open doors for you in terms of having the basic knowledge of how to do things. It'll allow you to read more advanced stuff and pick it up much faster than if you hadn't.

Below is a list I sent to someone on here a while back.

>
>http://www.reddit.com/r/webdev/comments/1eqaqo/best_books_or_online_resources_for_comprehensive/ca2w2dn?context=3



>PHP and MySQL Web Development (4th Edition)
>
>Beginning PHP and MySQL: From Novice to Professional
>
>Read the second book, do all the examples, then go back to the first book. Pay a lot of attention toward array manipulation. When you're comfortable with that, get into OOP. Once you do and OOP clicks for you, you'll be able to go to town on anything. I've heard a lot of good about Jefferey Way's video lesson courses over at TutsPlus. I've never used them nor do I need to, but I've never heard a single bad thing about their video courses. Their Javascript and Jquery is a great starting point. This is great stuff too if you're willing to put in the time.
>
>Professional JavaScript for Web Developers
>
>JavaScript: The Definitive Guide: Activate Your Web Pages
>
>Responsive Web Design with HTML5 and CSS3
>
>The Node Beginner Book
> Professional Node.js: Building Javascript Based Scalable Software
>
>Paid online "schooling":
>
>http://teamtreehouse.com/
>
>http://www.codeschool.com/
>
>Bonus:
>
>http://hackdesign.org/
>
>
>I've got a shit ton (Excuse my French) of books in print and E-Format that I could recommend, but it would span a couple pages. Anything is easy to learn so as long is it's served in a hierarchical format that makes it easy to absorb the information. A year ago I started to learn Ruby and using ROR as a framework. I can say it's been quite fun and I feel confident that I could write a fully complete web app using it. I started node.JS a few months ago, but it's been on break due to being sick and some unexpected events.
>
>My knowledge is extensive only because I wanted it to be. I'm not gifted by any means nor am I special. Not by a longshot. Some people are gifted when it comes to dev and design, most are not. Most only know one or the other. I forced myself to learn and be good at both. I'm 23, I started when I was about 12. I'm only breathing more comfortably now. I know a load of people on here and other sites who make me look like complete shit.
>
>
>Also for what it's worth, sign up to StackOverflow. It's the bible and holy grail rolled up into one site. It's amazing.
>
>Also;
>
>Hattip to /u/ndobie
>
>> CodeAcademy
> Team Treehouse
> CodeSchool. This is more programming but still very useful & has free stuff.
> Tuts+
> Google. Probably the best way to find out how to do something specific.
> This subreddit. If you have any questions about how to do something, like parallax scrolling, try searching for it, then ask, make sure to include an example of what you want if you don't know what it is called.

Quite frankly, what did you expect? Every one starts somewhere.

http://stackoverflow.com is your friend. It is a great resource and you will be able to find a lot of information there.

Now, in regards to the technologies you want to learn, you need to start with the basics. Javascript is arguably harder than the rest, so I think your focus should lie there. You should be asking questions like:

• What is the document object model? How does it get rendered?
  
• What is the concept of object oriented programming and how does it work?
  
• What makes Javascript such a powerful language?
  
• What is jQuery and how does it make traversing the document object model easier?
  
  After you've learned those basics, you then need to evaluate the trends and topics in your workplace.
  
  
• What are recurring topics?
  
• What are their goals?
  
• Where do you fit in with the team?
  
• What part of their code do they consider the weakest (poorly written/designed)?
  
  Then you can focus on certain things. For instance, if they feel that most of their goals are related to user interface design, you may want to consider learning about more HTML and CSS (arguably the easiest of the three).
  
  However, if they feel like they need to add more functionality to pages and build backend code, you will probably need to learn more Javascript and jQuery. Remember, jQuery is a Javascript library and learning both together is the best route you can take (in my opinion).
  
  Here are a few resources which I used to get a better grasp on certain topics (quite frankly, I never finish books because all of this information is online).
  
  http://www.amazon.com/JavaScript-jQuery-The-Missing-Manual/dp/1449399029
  http://www.amazon.com/HTML5-Missing-Manual-Matthew-MacDonald/dp/1449363261
  http://www.amazon.com/CSS3-Missing-David-Sawyer-McFarland/dp/1449325947/
  
  All of the Missing Manual books are fairly well written and will give you a lot of insight on those languages.
  
  However, if you prefer to be taught rather than teaching yourself, some good resources like these may help you:
  
  https://www.codeschool.com/
  https://www.codecademy.com/
  
  Both of these websites are tailored to teaching you to code within your browser. I've found both of them to be excellent.
  
  Some resources which you will want to keep in handy:
  
  http://code.tutsplus.com/tutorials/the-30-css-selectors-you-must-memorize--net-16048 - Great tutorial on CSS selectors that may prove invaluable when working with CSS.
  
  http://diveintohtml5.info/ - A very well made web page regarding HTML5, its new features, and some other interesting topics.
  
  http://api.jquery.com/ - The documentation for jQuery. I know this can be found easily, but I can't stress enough how useful it will be to have this page open while you are reading through jQuery code.
  
  ...and much more. You will find more information online everywhere. If you feel like you need more information, feel free to PM me.
  
  Remember:
  
  "If you can't explain it simply, you don't understand it well enough" - Albert Einstein
  
  This is only the beginning of your long journey if you choose to stay in the development field. Good luck!
  
  Edit: Thank you so much for gold! If anyone else wants more information, feel free to PM me. I don't have anyone to talk to about web development XD

> Oh man that's a load of tech

See! My problem is it doesn't feel like that to me.

> I basically think to choose the right tech for my work instead of learning every technologies out there

This is exactly what you SHOULD do! Maybe try something new in your free time now and again if it tickles your fancy. But learning in your free time should always be something fun!

Me, I have used all of the above. Everything up there, I learned mainly on the Job and the main reason I shied away from Zend Framework is that it's the only one I mentioned that I have never used.

Remember: This is 8 years of experience with 7 years beeing the sole developer in a company that became more and more dependend upon my skill plus 4 of those years I was working two jobs.

> How did you deal with degree requirement?

There was none. In my line you had to earn credits to move ahead with your education but if you earned no credits that did not mean you had to exmatriculate.

> That was a bold move and inspiring.

Sorry, I don't understand, what was?

> I use bootstrap sometimes I'm lazy hahahs.

I am too XD. And I do too, mostly on pages where SEO is not quite as important or where the load is high anyway so a couple more kB don't hurt, I try to trim it down as much as possible though.

> KISS DRY is amazing principle.

Full disclose: Not mine! And yeah, I think so too, everytime someone joins me at my desk they giggle because of the Postit with "KISS DRY!" on it that is stuck to my screen. Only other developers understand.

> You have time for playing games now?

I would spend a LOT of time learning earlier in my carrer and I still do when I've found something that's fun to pick up. (Gulp and Sass just made my day! I could not stop playing around until my workflow was perfect. Better than some of my games.) And I always enjoy reading a good Book that hones my craft. The pile of books on my desk is actually higher than my screen.

But back then, and still today, I am a gamer! My weekend will be filled with Arma 3, Stellaris, Kerbal Space Program, Crusader Kings and/or Project Zomboid. But I have shed my addiction to MMORPGs so I guess I'll also be doing laundry and the dishes... bah.

Have a nice weekend.

I buy books because they go into a lot more details, or often are written really well, and easy to follow. Also, it's really nice to read paper. Often I keep books in the office as it's a quick and reliable way to research a topic in-depth without scrolling through hundreds of shit articles on a particular (and even controversial subject).

I really recommend these:

High Performance MySQL: Optimization, Backups, and Replication - I've read snippets, but it's recommended a lot and very good for more advanced readers.

SQL Antipatterns: Avoiding the Pitfalls of Database Programming - VERY beginner friendly, easy to read, follow, provides real and common scenarios and explains the anti-pattern, it's problems, the reasons to sometime excuse their use, and solutions. I love this book.

The Go Programming Language - Very good read, not TOO technical jargon, very nice to read, explains in depth and in an understandable way.

I've had plenty more over the years, but these are my current I have at home. Still more on order. :)

>Is there something wrong with me? Or is this a normal thing?

No, programming challenges are more about general problem solving via coding than the ability to write functioning apps. You have experience in the latter and not the former so will not be as good at coding challenges.

But like everything else practice is what makes you good at something so if you keep trying them you will be able to learn to solve them. And I think it is worth doing so, they teach you to techniques to solve some harder problems you can face in real world applications, though you might not see them as often. Overall they can make you a better programmer.

But there is a limit to their usefulness, like if you master app dev you don't master coding challenges, if you master coding challenges you won't master app development.

Solving the problems of coding challenges is a skill. It can be learnt like any other skill. I think it is worth learning how to solve them, but there is no need to become the best at solving them. If you are having trouble with all of them I highly recommend reading Think like a programmer which teaches how to better tackle problems you face and break them down into easier to solve chunks.

---

Some interviewers will ask you to solve a coding challenge. Through not always and the ones that do often use the same challenges (fizzbuzz is a classic one). Not being able to solve them will hamper some of your attempts to get a job, but won't stop you from getting any job. It won't even stop you from getting a good job as better places often ask better problems that are more relevant to the job rather than some random challenge they found on the web.

In case someone wants to read more about the whole thing.

I started by writing code to handle numerous image formats. I wrote the code in PHP but in my tests I found it's kinda slow. I asked myself if I could make it a lot faster if I tried another language. So I tried Python but it wasn't any faster. Then I rewrote one image format decoder (I think it was PNM) to Delphi. Why Delphi and not C# or C++? Well I just prefer Delphi. It was about 50 times faster without any optimizations.So I rewrote image decoders to Free Pascal (because it's more portable than Delphi and I can compile the code for pretty much any operating system). At that time I already had about 180 format decoders written in PHP. Why didn't I switch earlier? The code wasn't "too" slow but at some point I felt like it should be faster. Many of the formats allow images to be at most 320x200 so decoding such small images is always instant and you don't really feel any difference whether it is 0.05 or 0.001 sec.

Then I started adding more formats. Once you wrote decoders for that many formats it's pretty easy to add just one more and then one more and one more. How did I know how to wrote the decoders? Some of the formats are nicely described on Wikipedia. For example BMP: https://en.wikipedia.org/wiki/BMP_file_formatSome I found described in that book: https://www.amazon.com/Encyclopedia-Graphics-File-Formats-Reference/dp/1565921615

In case of other formats I just googled "NameOfFormat structure". And for many formats I had to try multiple options. For example I knew an image is 160x200 so I tried reading the bytes as RGB 24 bpp, then Grayscale 8bpp, Mono 1bpp then some less popular options like YUV 12 bpp Palette 4 bpp etc. After trial and error I was able to figure out how this format should be decoded. And sometimes I just wrote to the author of the format asking for details.

Image filters (sepia, grayscale) came next. I am way less passionate about this than about file formats so I don't have that many filters. At least not yet.

Hi James!

One of the best books for a novice web developer/designer (and not just novice, for anyone who wants to get up to speed with the newest editions of HTML and CSS) in my opinion is the "Learning Web Design" by Jennifer Robbins. The 5th edition was published in May last year, so it's pretty recent. You won't be learning any outdated stuff from this book.

The book is quite big, with around 800 pages, but the author is really great. She explains everything you need to know and she explains it really good. Throughout the book you'll be building an example web site by doing a lot of exercises.

The book starts with an explanation of how Internet works in general. It doesn't go too deep into this topic, just enough for a beginner. You'll then learn HTML, and after that CSS. There are two chapters on JavaScript, but it covers only bare essentials. You'll need another book(s) for JavaScript, though. The one I would recommend is Head First JavaScript Programming, which somebody already recommended it, too.

The Head First HTML and CSS and HTML and CSS: Design and Build Websites (also already recommended by other users here) are also great, but they are a little bit old now, as they are from 2011. Not that you won't learn anything from them. You could read these two, and then the book by Jennifer Robbins, so you get better familiarity with HTML 5 and CSS 3.

>would you say this is critical knowledge to be a good web developer?

Not really. Most people are out there solving business needs. Even if you're working for a web app, the majority of it is taking a business problem and building and designing a solution around it in whatever way makes the most sense. How good the architecture is, is really not super important because you're likely not going to be supporting enough customers that throwing more hardware at it can't solve. Knowing how things work and how to build maintainable software, is more important than knowing obscure CS fundamentals inside and out.

But what you described sounds more like something from Amazon, Apple, FB, MS, Google, or other large tech company. They want true blue software engineers, not someone who can make them a pretty landing page. I know from first hand experience that FB interviews for JS developers hit heavily on memory managment and Amazon doesn't give a shit what language you program in. Cracking the Coding Interview is a good way to study for all of those (but you're not going to memorize that book in the time you have).

Triforce is right about the Jon Duckett book. It is an excellent resource that is pretty to look at, as well.

I learned all of my HTML5 & CSS3 basics from Learning Web Design by Jennifer Robbins. It is a great resource, and provides great design exercises for you to practice on.

Given your experience, you will need to bypass the first few chapters. Fortunately, the book is well-organized. This will allow you to only focus on the your particular area of need, and help when referencing the book after you finished learning the basics.

You don't have to copy or mimic. Learn basic graphic design structure taught in schools. The most basic system imho, is the Swiss Grid System.

https://nicolamurphy17.wordpress.com/visual-literacy-2/research/the-swiss-grid-system/

It is based on readability and graphic structure. It shares a lot of it's core to current CSS grid libraries today. Looking back at graphic design as a base is very valuable as it is visible and pretty explicit in it's representation.

I originally came from graphic design in 1989. I taught myself HTML and CSS in 1995 after doing manual layout, poster art, etc. That led to flash and actionscript (won awards, featured in taschen books, k10k, etc.) This then led to more multimedia and interactive work, Stewart Little screensaver in flash, Time Warner road runner broadband experiences for their "new high speed internet" launch using SMIL, actionscript, and some early J's work... Flash begins to die and JQuery starts up...and then the dot com crash.

I leave the web world to return to school for architecture. I end up with a master's degree from a top school doing theoretical architecture and using lots of computation, python, to analyze environments and the placement of large scale media and interactivity (a ton of work for large scale LED in Time Square, sports arenas, etc). At the same time I teach myself Django, sql alchemy, flask, and all of the other python dev tools. I use this for data aggregation and presentation. And now, I have tackled Dart, Vuejs, Angular Dart, Flutter, and finding new ways to use the as tools to keep pushing forward.

With all of that, my initial education in pre digital graphic design principles has been as important as anything else; to quickly visualize a design and it's technical structure is an incredibly valuable asset across creative fields. So...learn some basic graphic design layout principles and use that to attempt to understand design from a structural standpoint...how would you construct what you see. The Swiss Grid System is a nice basic foundation that almost all grid systems today are inspired from, if they know it or not.

A good book on the topic

I rather like this book, but I read it many years ago: http://www.amazon.com/CSS3-Missing-David-Sawyer-McFarland/dp/1449325947/

As for fonts, it's okay to use 2 fonts, but generally don't use more than that. Less is more. Here's a good website that lists good Google web fonts (and some font pairings): http://hellohappy.org/beautiful-web-type/

Also for medium/larger sized projects, I recommend using a framework like Bootstrap, follow their markup and you can restyle after. This way you can have more consistent look.

Some people might sometimes recommend Javascript: The Definitive Guide but that one's really more of a tome or reference book. It's sort of the be-all, end-all of Javascript, but really REALLY not fun to learn from. Very dense and dry.

I've heard really good things about JavaScript and JQuery: Interactive Front-End Web Development. Or you could get the combined HTML, CSS, JS set.

I don't know those first-hand though. I've just heard good things and the design is beautiful. First-hand, I know that JavaScript & jQuery: The Missing Manual is good. I really like The Missing Manual series in general.

Work on your code/portfolio in your spare time and apply to any job that interests you.

In terms of how to improve your code, I'd take a look at these resources:

HTML/CSS

• http://learn.shayhowe.com/html-css/
  
• http://learn.shayhowe.com/advanced-html-css/
  
  Javascript
  
  
• http://javascriptbook.com/
  
  PHP/MySQL
  
  
• http://www.amazon.co.uk/Learning-PHP-MySQL-JavaScript-Javascript/dp/1491918667
  
  Or look online for any good resources for whatever technology you want to get into.
  
  Good luck :)

First off I would look at what companies in particular you want. You could even start networking if they have an online presence, but at the very least you could find out what is booming in Iowa or KC based on the actual job market. Learning a language for the sole purpose of learning the language is kind of a waste of time, since it seems like you already have years of web dev experience in one form or another and aside from basic familiarity with an IDE and source control I doubt there's much difference to an employer who wants to know if you're a good fit with the people and team(s) you'll be working on.

Specializing is always good, but this is something that you can write your resume to reflect. Remember it's not a meritocracy. Companies don't hire best candidates, they hire best impressions. Becoming a "Master" in any language in the span of 7 months without actually working on a project team is basically impossible. But you could learn the fundamentals of a few, take a few Udacity courses for instance...

This and more is covered in a really good book by John Sonmez called Soft Skills http://www.amazon.com/Soft-Skills-software-developers-manual/dp/1617292397

There's a lot of good general coding advice on here so I'll keep my post relevant to life stuff. I came into web development after being an undiagnosed bipolar alcoholic for several years. Originally, I wanted to become a web designer but I quickly grew fascinated by the back-end development of a site and my skill set grew quickly.

One of the hardest challenges you will face is when this stuff is no longer new and exciting. You will have moments when it's hard to push yourself to code but like running, you have to push past the wall. A good book is Softskills for Software Developers https://www.amazon.com/Soft-Skills-software-developers-manual/dp/1617292397 you should check it out.

Here is an interactive page where people can visualize how Quicksort works, this is one of the most widely used sorting algorithms, once understood you can pick any of the other popular ones: Bubble, Insertion, Heap, Selection, etc. CtCI — Cracking the Coding Interview is a good book written by an engineer who used to be part of the recruitment team at Google and other "Big 4" companies, I really recommend it, every page is worth its penny*. Leet Code is also a good resource to learn and practice algorithms, most of the exercises have articles with good explanations of how to solve the problems.

• Although, as everything else, you can download it as a PDF file.

Hhm. Well, first of all, I think you might have a hard time finding a book that will teach about both design and web development. Each of those are complicated enough to write separate books on. I think you'll be better off by finding two separate books (one on web dev, one on design) than finding one that combines both.

A kind of the same goes for Web. Dev. This is such a broad term, that you will hardly find any book that tries to cram in every possible aspect of web development. If you are a bit more specific and focus on a specific technology (like NodeJS, ASP.net with Angular or just plain old PHP, MySQL and JavaScript ) you'll get more value for money. There are more generic books out there, but the technologies (especially for web dev) change almost daily and books simply can't keep up with that. If you'd ask me, I think you'll be much better off having a good understanding of JavaScript in general before you move on to a specific stack or framework.

Head first books are really good except you should get the up to date version.

http://www.amazon.com/Head-First-JavaScript-Programming-Freeman/dp/144934013X

I read that javascript book back in the day and i definitely liked it. I'm not sure what's different in the new one but with programming it's always good to be up to date. If you can't get it then this one will do. Everything in there still works and javascript still has pretty much the same idea as in that book.

The best way to learn to program while writing for the Web is to use Dart (http://dartlang.org). It's a Google-invented alternative to JavaScript that's sane, complete, and so easy to learn. And it just so happens that there's a really great book that takes a true beginner through the whole process: Dart for Absolute Beginners

If you really want to learn, I think a good start for you would be to read this book it was a good start for me and a tremendous help. It should also cover the basics of everything you need to know. Also this video helped me a lot as well.

The Visual Display of Quantitive Information is a great source for history and inspiration on Data Visualization and analysis. If you do end up gravitating more towards design I would also recommend Grid Systems in Grpahic Design by Josef Müller-Brockmann.

​

https://www.amazon.com/Visual-Display-Quantitative-Information/dp/1930824130

https://www.amazon.es/Grid-Systems-Graphic-Design-Communication/dp/3721201450

I would highly recommend this book:
https://www.amazon.com/Soft-Skills-software-developers-manual/dp/1617292397

I would also look into joining a local Toastmaster's club.

If you do those 2 things you'll definitely develop some great soft skills.

I learned a lot about it from reading this guy:

http://www.amazon.com/High-Performance-MySQL-Optimization-Replication/dp/1449314287/ref=sr_1_1?ie=UTF8&qid=1407623587&sr=8-1&keywords=high+performance+mysql

But things like normalization and denormalization are foundational to building the table schemas right from the get-go. I don't remember if the book covers it, and I don't have it on hand to check. You can google search that stuff easily, though.

buy this book: http://www.amazon.com/Learning-MySQL-JavaScript-Step-Step/dp/0596157134
and never look back.
If you want to go beyond any basic template for wordpress or anything else, you should check out PHP a little bit. Its super fucking easy.

I strongly recommend reading Gayle Laakmann Mcdowell's Cracking the Code Interview, or watching one of her lectures on the topic. Although her book goes into detail on the types of questions that can come up in these interviews, the general advice she gives in this lecture is solid gold.

There's always new technology to learn, especially if you're pursuing the "full stack engineer" title. Do you know all the details of browser performance? Familiar with http? TCP? TLS? Deep understanding of MySQL?

But really, technology receives too much attention, especially from junior developers. Most of the attributes of senior engineers are people-oriented, either in how you interact with others or the attitude you yourself take when approaching situations. Actually, I'll just stop here; go read that last link and listen to someone who tells it better than I can.

Cracking the Code Interview is an excellent book if you haven't already checked it out. It's more then just coding problems too. She tries to cover everything that you might need.

You might consider one of the "Head First" books. Some of them are a little out of date; they have a very distinctive style that you may really like or really hate. I think the style could be useful if you are dipping in and out of reading at work. Two examples:

https://www.amazon.com/Head-First-HTML-CSS-Standards-Based/dp/0596159900

https://www.amazon.com/Head-First-JavaScript-Programming-Brain-Friendly/dp/144934013X

They're really two different areas, and you could cover multiple books writing about both (without even getting into development languages).

For a simple introduction to HTML and CSS, try this book by John Duckett.

If you want to learn about client-side and server-side development, try these:

• PHP and MySQL Web Development
  
• JavaScript, A Beginner's Guide

PHP and MySQL Web Development (4th edition)

I used this book. I just read every chapter, took notes, and quizzed myself at the end of each one.

https://www.amazon.ca/dp/1593274246/