Thanks FCC - I got my first job as a front-end developer!

Thanks FCC - I got my first job as a front-end developer!

I appreciate your help I really do. It’s just that it seem that whereever I apply there is always something wrong. Either it is that I have the wrong kind of engineering education or it is that I lack experience or it is that I am not socially competent enough.


No, probably not, but not knowing your entire work history and education background I was suggesting various things that help various people.

The theme is keep trying lots of things.

I got a job with no tech education or experience without an internship, but location, demand and a whole host of other variables will mean what works for either of us will likely be different.

It is very frustrating and disheartening, I know. Every rejection I received from a job I knew I could do with my eyes closed really stung and made me doubt whether it was even possible. But really just trying lots of things is what paid off.


Thanks for the advice. Maybe I should start running a dev blog to detail my thought processes while doing the rest of the FCC curiculum.


I would encourage you to learn PHP 7 and SQL as well.

PHP is actually a lot easier to learn than Node.js (Just because it’s JavaScript doesn’t mean it’s easy)

  • PHP 7 is SUPER fast !!
  • PHP 7 is wayyyyyy easier to get practical stuff done than it is in Node.js
  • PHP 7 is probably the MOST widely supported programming language to build internet based software
  • PHP 7 is very similar to JavaScript (closures, anonymous functions, callbacks, etc.)
  • PHP 7 has a lot more array functionality than JavaScript (eg. built in set intersects, differences, and unions)


// PHP 7
$set = [];
array_map(function(){}, $set); 

// Node.js
let set = [];{}); 

SQL is just super important. Period. You can use it with PostgreSQL, MySQL, Oracle, and SQL Server.

I’ve spent 1,000+ hours studying Node.js and 1,000+ hours studying PHP 7 and I can say without a shadow of a doubt, PHP 7 is A LOT easier to learn once you get used to the scary syntax.


:congratulations: :confetti_ball: :sunny: :fireworks:


Hi, Lupe,

Thanks for sharing your story – would you help me out with GitHub Pages: I don’t really understand something about them: do they require “Jekyll” and does that in turn require “Markdown”…I’m interested in the free web hosting for my portfolio (at least for now) but the documentation isn’t very clear to my beginner’s mind about all the various software dependencies involved (“Jekyll” seems to require the language Ruby and the RubyGems package manager to be installed as well).

So any insight would be very much appreciated; thanks in advance!


Github Pages does not require that you use Jekyll, it just happens to be quite well set up for it.

If you have it configured correctly, all you need is HTML, CSS, and JavaScript files to have good looking and impressive github pages sites. You can also use complex libraries such as React on GH pages. It’s worth learning, but start with understanding git and github first… Pages makes a lot more sense once you get the other stuff.


Hey, Jackson,

Thanks – is there some kind of comprehensive A-to-Z Step-by-Step for Github Pages somewhere online?? Indeed, the configuration is what’s got me scratching my head and even my butt! :wink:

Otherwise, I may just go and pay for Bluehost now – $181 for three years with privacy and SSL plus free domain name and unlimited e-mail and domains, bandwidth, etc. (sorry for sounding like a shill but it’s a great deal, even if it is shared hosting)…I already know WordPress and ePanel but I’m interested in Github Pages just 'cause I don’t actually have any kind of portfolio at all right now so paid hosting would be a waste for a month or so…


Start here:

Ask for help if a particular step trips you up.


Sorry, I should’ve previously made clear that I’d already been there – those instructions are good I’m sure but I’m really looking to get a “mind map” of it all…and I can already sense that you’re right: once I understand Git and GitHub, GitHub Pages will make more sense (and I’ve actually already started reading on them, such as at,, and

But for now, let me ask in another way:

  1. Might the Windows Terminal (the Command Prompt) be preferred over GitHub Desktop for any reason when it comes to GitHub Pages – or vice-versa?

  2. Once I publish my GitHub Pages site, do I simply create new GitHub Pages webpages using a plain old text editor like Windows Notepad?

  3. How would Jekyll improve on the process in Question Two above, assuming that that’s how it works?

  4. Whatever is the point of Jekyll – how exactly is it so complementary with/of GitHub Pages? It seems to require the installation of Markdown, in turn – certainly knowing how to use Markdown (probably much easier than even HTML, to be sure, which it seems to aim to “replace”) – but why all these “layers”…what’s made more effective/efficient by all this interposing software???

  5. Is “the GitHub Pages interface” (or “the GitHub Pages workflow” or whatever the proper term might be) a kind of CMS, in effect, using the “Git conceit” (of version tracking) to manage webpages in place of a typical CMS??

BTW, in case you’re wondering, I’m one of those apparently few (or so I’ve been reading) who prefer to plan and plot out a computer program instead of jumping right in coding, fingers all a-blazin’ (hence these questions) – thanks again! :wink:


Some examples:
GH Pages hosted version:

Take a look at the example above, and read the source code in the repo. Just look at the index.html file and the JavaScript and CSS files. Those are being served up by GH Pages to produce the simple app in the second link.

All GH pages does is host those files and provide a url for them, much like a simple webserver would.

I have recently set up a blog using Jekyll too:


What Jekyll allows me to do is write my posts in a simple mark-up language called Markdown, which is a little nicer to use than raw HTML. I used a Jekyll project called Poole to bootstrap the blog since I didn’t want to over think the design or implementation details.

It’s sorta like using github as CMS, but not really. It’s still just simple static files being served up. There is no database involved.

Once you have website files in your repo and adjust your settings so that github knows to serve them up, the rest is automatic.

1 Like

To answer your other questions:

  1. Command line or desktop client doesn’t really matter. I prefer the command line because I can use it on any computer without having to download anything new, and it is useful if I need to SSH into a server. I spend a lot of time in the terminal at work. But use the desktop version if it helps you get started.

  2. You can use Notepad… But don’t. For your own sanity use a proper editor such as VS Code or Atom. They manage multiple files better, dont mess with utf encoding, and provide helpful things like syntax highlighting.

  3. Jekyll only improves things if it suits your use case. You don’t always need it. I’ve only ever used it once, but I host most of my projects on GH pages.

Hope this helps.

1 Like


Thanks so much, Jackson; I’m able to fill in a lot of that “mind map” now! I especially appreciated seeing your examples (the URLs)…and BTW, your two posts were interesting, especially the reprint of the Medium essay on learning styles! I’m not an educator but had to read up on pedagogy earlier this year (a bit of a long story) so learning about Vygotsky’s Social-Constructivism and Zone of Proximal Development brought up some memories!

  1. Ah, good to know: the command line option is immediately accessible from any machine, guaranteed (makes sense since it’s the command line, the terminal, after all, but for some reason I didn’t see the availability implication).

  2. Yeah, sorry, I actually use Notepad++ for code (still way too much of a n00b to use an IDE!); I’d mentioned Windows’ Notepad by way of emphasizing the extreme degree of simplicity possible.

  3. So in what use-cases could Jekyll possibly make sense?? Sorry if I seem all obtuse and “dunder-headed” here but my imagination fails me (again!)…I just can’t see what’s solved by having to install and learn Markdown and learning to install Ruby and RubyGems and then learning and installing Jekyll…

Thanks again!


If you intent to have a content heavy site, like a blog, Jekyll makes sense, especially if you don’t want or need the complexity of a CMS and databases.

If you are creating front-end apps (like most of my github repo), then Jekyll doesn’t really help.

Here is some reading on the perks of Jekyll:

1 Like

Super – another reference; I love references!!

Never even knew that was a thing…static site generator??? Wow!

One final question, please: so is it possible to have a static portfolio site showcasing dynamic web apps?

I ask 'cause to my way of thinking, the webpages themselves are static so as they are “containers” for the web apps – which are dynamic by definition, right? – this should be impossible.

But then again, maybe web apps “run on their own,” “independent” of their “webpage-containers” – right? – which is maybe how something like Google Maps first got started way back when, back in the days of static-y Web 1.0 (IIRC!!)…



Congratulations (I know, it’s only a year later)! I just came back from visiting a friend in Portland a few days ago. I enjoyed reading your post and all the excellent advice you provided. It’s encouraging to know that you stuck with it (even after taking a few weeks/months off)…and eventually you picked up where you left off and still met your objectives. Nice job!

1 Like

Wow! I really enjoyed hearing about your experience. It’s great motivation to keep me going. Congratulations and good luck with your first job. :grinning:

1 Like

This is awesome and motivating, good luck :wink:


That article is really amazing!