0
0

[–] captbrogers ago  (edited ago)

Though others have already said it, I'll reiterate and expand a little: practice. Like any other skill, practice is essential to becoming proficient. Something to remember (from Adventure Time, if you've seen it), "sucking at something is the first step to being sorta good at something". You'll suck right now, but you'll only suck when you compare yourself against others that have been doing it for a long time or seem to be naturally gifted with it. There will always be someone better, so in a way you may feel like you can never keep up. Accept that feeling, know that you won't be able to learn everything or sometimes as much as others. Learn what you need to do what you want to do, and then be happy with that. Otherwise, you may burn out fast trying to keep up. Burning out is one of the worst parts of programming (though not unique to programming) that I've experienced.

You may find yourself constantly asking, "Well, practice is good, yeah, but practice what? How? How often?". I always tell everyone that is starting out to do the same thing, re-invent the wheel. There are a dozen popular software packages that do anything worth while unless the capability is "bleeding edge" new to browsers. So using Django, write a blogging application. It doesn't have to be the best, use Twitter Bootstrap or Zurb Foundation or MaterializeCSS to handle the looks of it, but you write all the backend. At least with a PHP framework or Rails, I recommend doing it with as few 3rd party packages as possible. Don't just include a dozen packages and call it good, roll your own authentication system. Don't use it in any live site, but learn how it works in a basic form. Be able to login and logout (dealing with sessions), reset a password using tokens (hashing and one-off events), etc.

Keep up the work, don't get discouraged when you bang your head against the keyboard for an hour because nothing is working right for you. We all have those days.

0
1

[–] FFX01 0 points 1 point (+1|-0) ago 

I just started doing a flask mega tutorial that goes over how to build a complete blog site with accounts, posts, comments, following, blocking, the whole shebang. I'm about half way through after spending 12 hours on it. I'm learning a lot about how a stack is supposed to work, and I have to say, I really like Flask. The tutorial is really in depth. It's written by the guy who wrote the O'Reilly book for Flask, so I'm sure it keeps up with conventions.

Link to the tutorial if anyone is interested

0
0

[–] captbrogers ago 

Coincidentally, I've been thinking about learning Python for websites. Thanks for the link.

0
1

[–] DiggToRedditToVoat 0 points 1 point (+1|-0) ago 

How long have you been studying?

0
0

[–] feministwitch [S] ago 

I started html a long long long time ago but I started getting into full stack something like six months ago...

0
2

[–] bufferoverflow 0 points 2 points (+2|-0) ago 

The way that works for me is to find a design online and try to get as far as I can replicating it on my own and then looking at the original source to help get me over any difficulties. Practicing is what builds a lot of experience for me.

0
1

[–] feministwitch [S] 0 points 1 point (+1|-0) ago 

Do you download the content first?

Do you now any good source about floating? It makes me go crazy....

0
0

[–] bufferoverflow ago 

Sometimes I will download content, sometimes I will just make new content with The Gimp. With floating, are you referring to floating divs? You might want to check out node.js tutorials

0
4

[–] TheOneAndOnlyCrumpet 0 points 4 points (+4|-0) ago 

I wouldn't worry too much. If they accepted you then they know your perfectly capable. Don't be afraid to let them know your new to this and they should have patience.

As for recommendations I suggest you just go over what you will need to be able to do for your job. HTML is rather easy so it shouldn't be too difficult.

0
0

[–] feministwitch [S] ago 

I'm actually having trouble with getting clear job specifications... management says one thing, colleagues say another...

If you had to chose between content management and newsletter creation which would you chose? Same pay and all..

0
0

[–] magicmu ago 

If they accepted you then they know your perfectly capable. Don't be afraid to let them know your new to this and they should have patience.

This is a crucial thing to remember -- everyone has to start somewhere, and it's better to ask for clarification on something than to feign knowledge and waste everyone's time. HTML isn't overly difficult, but email newsletter formatting can be tricky to get right in every browser and mail client. Don't be discouraged!

0
2

[–] feministwitch [S] 0 points 2 points (+2|-0) ago 

I'm not exactly afraid. I'm good with html and CSS, I'm nervous because I want to grow towards web development and it's the first job where I can see myself getting somewhere.

I supose I just needed some encouragement. :)