3 ms·

Use the time to learn to code, you can totally get in to the industry starting that way. Also once you got the basics try to think of a simple project. I'd eve

Use the time to learn to code, you can totally get in to the industry starting that way. Also once you got the basics try to think of a simple project. I'd even help you find one, just comment below. (depends a lot on what you want to learn). A project is really the best way to learn things beyond the very basics, learning without a clear goal is quickly demotivating. As a bonus you have something to show afterwards. I learned web stuff while I was in school and became a front-end developer afterwards. Now I dipped in to AI and got an AI related job (not as a dev, but having some experience helps to propel you in the direction you want to go).

TurkishPoptart 7y ago
Yes! I certainly am trying! And it's true, I have a number of project ideas floating in the back of my head, but I rarely realize them, which is a problem. Here's what I want to make: recipe-based website/app, in which user can choose one of four seasons, with perhaps a slider for {Vegetarian} or {Instant Pot} (or something), and it spits out some recipes. The ingredients <div> will default to serving for 1, but user can choose servings for 2, or 4, and the app re-calculates (1 cup -> 4 cups, etc.) I personally want to learn (and am more interested in) the backend stuff to make it work. And I am worried that even if I get it work, I will get lost in the CSS mess of trying to prettify and arrange things. But I should just focus on learning to and making a working skeleton app first, I suppose. Thanks for your comment.
- anotheryou 7y ago
  That sounds like a great first project. I recommend to break it down in to sub-steps where it's your choice if you want to start front to back (paste a recipe, make it pretty, than add calculations, than put a DB behind it etc) or the other way around. I have a slight preference for starting from the front so the UI does not get skewed in the direction the technology leads you. Going front to back in ideally also leaves you with presentable stuff before everything is done: A pretty website with your fav recipe, A pretty website with your fav recipe and an ingredient calculator, ... About CSS: I guess it makes sense to learn it a bit, but as you want to dive in to the back-end anyways, maybe also check out frameworks like bootstrap with a nice material design theme¹. I'm not sure if it teaches you some bad practices though, so take it with a grain of salt. For my taste the html becomes to ugly, I prefer to keep most of the design part in my CSS. Oh and if you need help the guys on the freenode IRC are very friendly. Just make it as easy as possible to help them: isolate and reproduce your problem, for front-end stuff make a "fiddle" at jsfiddle.net. ¹ e.g. https://ayroui.com/ https://ayroui.com/ Also helps building "mobile first". Today consumer stuff will mostly be consumed on smartphones.
  - anotheryou 7y ago
    Maybe you wan even find a design student who wants to do the front-end. If you show that level of collaboration and have something even prettier to show that's a win win :)

TurkishPoptart 7y ago

Yes! I certainly am trying! And it's true, I have a number of project ideas floating in the back of my head, but I rarely realize them, which is a problem. Here's what I want to make: recipe-based website/app, in which user can choose one of four seasons, with perhaps a slider for {Vegetarian} or {Instant Pot} (or something), and it spits out some recipes. The ingredients <div> will default to serving for 1, but user can choose servings for 2, or 4, and the app re-calculates (1 cup -> 4 cups, etc.) I personally want to learn (and am more interested in) the backend stuff to make it work. And I am worried that even if I get it work, I will get lost in the CSS mess of trying to prettify and arrange things. But I should just focus on learning to and making a working skeleton app first, I suppose. Thanks for your comment.

anotheryou 7y ago
That sounds like a great first project. I recommend to break it down in to sub-steps where it's your choice if you want to start front to back (paste a recipe, make it pretty, than add calculations, than put a DB behind it etc) or the other way around. I have a slight preference for starting from the front so the UI does not get skewed in the direction the technology leads you. Going front to back in ideally also leaves you with presentable stuff before everything is done: A pretty website with your fav recipe, A pretty website with your fav recipe and an ingredient calculator, ... About CSS: I guess it makes sense to learn it a bit, but as you want to dive in to the back-end anyways, maybe also check out frameworks like bootstrap with a nice material design theme¹. I'm not sure if it teaches you some bad practices though, so take it with a grain of salt. For my taste the html becomes to ugly, I prefer to keep most of the design part in my CSS. Oh and if you need help the guys on the freenode IRC are very friendly. Just make it as easy as possible to help them: isolate and reproduce your problem, for front-end stuff make a "fiddle" at jsfiddle.net. ¹ e.g. https://ayroui.com/ https://ayroui.com/ Also helps building "mobile first". Today consumer stuff will mostly be consumed on smartphones.
- anotheryou 7y ago
  Maybe you wan even find a design student who wants to do the front-end. If you show that level of collaboration and have something even prettier to show that's a win win :)