Jump to content

rbrtsmith

Privileged
  • Content count

    4,039
  • Joined

  • Last visited

  • Days Won

    1

rbrtsmith last won the day on January 17

rbrtsmith had the most liked content!

About rbrtsmith

  • Rank
    ReferenceError
  • Birthday 11/16/1984

Users Experience

  • Experience
    Nothing
  • Area of Expertise
    Web Developer

Contact Methods

  • Website URL
    http://www.rbrtsmith.com

Profile Information

  • Gender
    Male
  • Location
    Manchester, UK
  • Interests
    CSS, JavaScript, Front-end Developent, and website performance.

Recent Profile Visitors

17,927 profile views
  1. Visual Studio Code

    You don't need to be an expert in Linux to get a junior front end job, even for senior roles you don't need to know any more than the basic unless you plan to work more in a devops role. The commands that @citypaul listed are enough for your use case at the moment. Going much deeper than that will mean you have less time to focus on front-end specific stuff. Remember while it's possible to land a front-end job within a year starting from scratch it is not easy and requires a lot of effort and a very focused learning strategy. Trying to master too much will result in it taking far longer to become job ready. As much as I hate WordPress eventually learning the basics of that and PHP will help you get into the agency type jobs that are typical places for juniors to start - but long term I'd not focus much on WordPress because places like BBC, Sky, Sainsburys etc do not go anywhere near WordPress and rarely use much PHP either.
  2. Visual Studio Code

    If on windows I'd recommend either installing Linux or using a linux like shell. I wouldn't waste much time learning windows specific commands. Most places these days are using Unix/Linux like environments (Mac OS runs on top of Unix). Most JavaScript / Node courses will be using Unix commands too.
  3. Visual Studio Code

    This is good advice. Just start off with basic cd commands and each day try learning a new command, write it down next to your laptop for future reference.
  4. Visual Studio Code

    A very simple Git process to do this (without going into detail) is: 1. Create a repository on Github (I assume you already have an account) -- Go you your profile, click on "Repositories" tab and then click the green "New" button, Choose a name and click on the green "Create Repository" button. Follow these instructions... …or create a new repository on the command line mkdir my-test-project cd my-test-project echo "# test" >> README.md git init git add README.md git commit -m "first commit" git remote add origin [url-to-your-repository] git push -u origin master [url-to-your-repsitory] will be git@github.com:[your-username]/[your-repository-name].git Then going forwards any work you do in this folder you can commit up by doing the following git add . git commit -am "your commit message" git push If you jump onto another machine you will have to clone this repository down from github git clone git@github.com:[your-username]/[your-repository-name].git cd [your-repository-name] Work on this machine then follow the previous steps to commit and push up that work. You have to ensure you have SSH keys setup on both machines. https://help.github.com/articles/connecting-to-github-with-ssh/ is a good set of documentation on how to setup and work with SSH. There is a lot more to Git than this, but I'm just showing the minimum you need to know to use Git to provide the kind of workflow you require across these multiple machines. Now the repository on GitHub shall be the source of truth for your project. Note - you can have as many repositories as you want, typically each project will be a new repository.
  5. Visual Studio Code

    I would recommend using GitHub over Bitbucket for any projects that are not private - reason being that Github has very good social tools and if you want others to see your work it's the way to go. Both are very similar but that's where I host all my open source work. Just don't be dumping private stuff up there. But if you're focusing on frontend you are unlikely run into issues like accentually posting up DB credentials etc as they're handled by the server. For your treehouse stuff I imagine you'll be using fake servers or using existing public APIs. If I am working on a project that has a bunch of variables / contstants that need to be private I dump them in a .env file and gitignore it. If it's to be consumed by others I also create a `.env_example` with example credentials so consumers have an idea of how to input their own.
  6. Visual Studio Code

    For those of us that are using a load of automated build tools we still use the browser to visually see and interact with our work. We have setups that auto-refresh the browser with our changes, and in some cases something called hot module reload where the component we are working on gets updated without the page even refreshing... However you are unlikely going to need to know much about these tools to land your first role as a junior dev. I'm sure the Treehouse course will introduce you gently to them.
  7. Free or Cheap Hosting

    This. Why are people always looking cheap or free?? If this is for your business then it's not gonna succeed by scrimping on the things that matter. If you get any real volume of traffic your site will go down. Even less cheap but still shared hosting will be flaky - what if another site on the server uses up all it's resources? Yours will grind to a halt. These cheap ones rarely give you SSH access which is a bare minimum these days. I couldn't imagine using FTP for deployment even 5 years ago.
  8. Google Analytics

    Many non mobile devices also use double pixel density etc, in fact most modern screens do this to some degree - ultra HD. Nobody should be concerned at all about how many pixels visiting devices have, just ensure that the UI looks great from 320px upwards and that images do not appear too blurry on high end devices. There's no need to over think / complicate this.
  9. There's no value in .[name] unless it's a .com, .co.uk, .io or similar. Hell I could register google.baz google.bar and they would hold no value whatsoever. There can be a lot of value in popular .com addresses though. The domain owned by the OP I'd imagine has not much more value than a packet of crisps unfortunately.
  10. Visual Studio Code

    You're at the beginning in terms of your journey to becoming a web developer. The course on Treehouse, I am sure will go into build tools eventually but they all require some knowledge of JavaScript so for now just manually refresh the browser to receive your changes. Just be patient and once you know JavaScript fairly well then that will open up possibilities around tooling and automating processes, tasks etc. I also wouldn't focus too much on plugins and so forth, I know many successful developers who barely use any. Focus on the treehouse course and for VS Code learn the common keyboard shortcuts and tools you are going to make heavy use of. Don't bother deep diving into things you might not need. Being efficient in learning things that add immediate value is critical if you want to get job ready quickly.
  11. Is PSD to HTML conversion service a profitable business?

    You missed the boat by 5 years...
  12. This thread is almost 8 years old!?!?!?! @Ashj welcome to 2018!
  13. If you hit a wall and feel like you've exhausted all your ideas then there's no harm in asking on a forum - or even emailing the tutor / others on treehouse etc. I still ask for help on a regular basis 5 years into my career. No matter how much experience you get in web dev there will always be others with more knowledge of a particular area, especially when people begin to specialise so just ask! Other developers are a goldmine of information and virtually all are happy to share that knowledge.
  14. Codepen isn't an editor as such, It's just an online playground for writing snippets and being able to see them rendered in the browser, the pens can be saved and quickly shared to others. So useful for getting feedback. As for actual code editor I'd argue Visual Studio Code is the best one around at the moment. I've worked with a lot and this stands head and shoulders above the rest. It is free too.
  15. Expect to see a load of party parrot spam
×