April 17 — Daily CodeNewbie Check-in Thread

#codenewbie #checkin #beginners #discuss

You are encouraged to use this daily thread to:

Ask for help (all questions encouraged)
Explore topics you’re curious about
Share something you’ve written or read
Celebrate your wins
Stay accountable to your goals
Support your fellow programmers

Happy Coding!

Interested in joining the twice-weekly live #CodeNewbie Twitter chats? You can find us on Twitter each Wednesday at 9pm ET (1am GMT on Thursday) and Sunday at 2pm ET (6pm GMT)!

Latest comments (12)

Vicente G. Reyes • Apr 18 '20 • Edited

Satisfied with my home page. Tomorrow I'll be going live on my Facebook Page at 11PM Asia/Manila. I'll be creating the database models for the data and the contact page.

This is what it looked like yesterday:

Vicente G. Reyes

Apr 17

Almost done with my local Covid-19 tracker side project which also uses contextualsearch's API to curate global news about the virus.

Tech stack is Django + Zurb Foundation + Vanila JS + Postgresql. Hosting is sponsored by Digital Ocean 😄

Kris • Apr 17 '20

How's everybody's week wrapping up?

David Ojeda • Apr 17 '20

Coffee is helping! ☕️

Jan Kosutnik • Apr 17 '20 • Edited

Question or shall I say questions:

How to get resume worthy experiences in Backend?
Do you think it’s harder than in FE?
Would you rather: learn something that might get you employed sooner, or would you pursue something you are more interested in?

Ben Halpern CodeNewbie • Apr 17 '20

Freelancing, even for mom and pop stores etc, or volunteering is a great way to get some kind of real world experience which you can put on a resumé. Otherwise, I think one really substantial project plays well compared to many little proof of concepts. Contributing to an open source project of any kind is also a nice thing to plop on a resumé.
I think pretty much any environment is the same "difficulty", because you'll always have to push the envelope. Frontend might be "easier" if you're only tasked to spin up an HTML page, but if you need to get into complex interactivity, build tools, etc. it all goes out the window. Complexity will creep up in any environment. I'd say focus on what interests you the most.
I'd try to find the space that is closest to accomplishing both, but I'd lean towards employed sooner in general. The sooner you're getting paid for this stuff the better—but you don't have to cherry pick stuff that is likely to lead to better employment opportunities from hearsay and speculation. Likely there is a decent chance of employment from any practical path you take.

I always suggest folks interview early and often, before they feel like they're 100% ready.

Embrace How Random the Programming Interview Is

Ben Halpern ・ Mar 4 '17 ・ 2 min read

#careeradvice

Jan Kosutnik • Apr 17 '20

This is not the first time that I came across an advice that one substantial project plays well compared to many little ones, and contributing to open source, I agree, is always a good thing.
I am currently getting more into Vanilla Js, because with limited Js knowledge I wanted to learn React, failed the first time around, but realized that core foundations are needed, therefor I am now progressing with VanillaJs. This also goes with job requirements in my area, where there aren't many Ruby or Rails jobs, even though I would really like to get more into Ruby and Rails.