Member Avatar for bo0ga

Just got an entry level web developer position the city. It starts in 2 weeks. I would love some tips on how to effectively prepare. I'm an IT major not computer science, so my classes focused more on systems and databases rather than programming. I had a really good interview with them, but I'm afraid they may think I know more than I do. I don't want them to ask me to do something and be dumbfounded. So I'm dedicating around 8 hours every day for the next 2 weeks to learn as much as I can. I have basic experience in HTML, CSS, Javascript, SQL, and Java.

So far I've downloaded video tutorials on HTML5, ASP.net, C#, Java (more advanced), PHP/MySql. I also plan on reading w3schools.com guides on CSS, Javascript, and JQuery. If I have any time left over then before my job starts I will look up video tutorials on Flash and Photoshop.

Am I doing it right? Any tips in general?

  • 3 Contributors
  • 3 Replies
  • 200 Views
  • 3 Hours Discussion Span
  • Latest Post Latest Post by bo0ga

Dani AI

Generated

Brief, practical prep to complement ’s push for hands‑on work and ’s onboarding/people advice. Two weeks is best spent learning the day‑to‑day workflows and producing three small, concrete artifacts that mirror real tasks rather than trying to cram every language.

Practical checklist (daily, hands‑on):

  • Local environment: install a simple local server (XAMPP/MAMP/WAMP or a single Docker container), clone a repo, and get a project running end‑to‑end. Verify one change can be edited, built (if needed), and reloaded in the browser.
  • Browser tooling: practice the Elements, Console, and Network panels; set breakpoints, inspect AJAX calls, and emulate mobile sizes. These skills save hours on day one.
  • Version control workflow: create a remote repo, make small commits with clear messages, open a pull request and learn to read diffs. Branch → small change → PR → review is the typical cycle.
  • Three micro‑projects to complete and keep in the portfolio: (1) responsive single landing page (HTML/CSS with a media query), (2) a tiny interactive widget that fetches JSON and updates the DOM (exercise DOM, events, and network debugging), (3) a minimal CRUD demo backed by the stack closest to the employer (simple PHP+MySQL or an ASP.NET sample). Each should be completable in a few hours and housed in its own Git branch.

First‑week on the job: read README/CONTRIBUTING, run the app locally, find a small, low‑risk first ticket (typo, CSS tweak, minor bug), and request a short pairing session with a senior to learn the repo layout. Emphasize clarity over claimed expertise: demonstrating how quickly one learns and how code is landed matters more than knowing every API at start.

Quick troubleshooting habits: reproduce locally before changing production, inspect server logs, use browser network/console first, commit early and often, and keep PRs small. These practical routines convert two weeks of study into immediate, visible value on day one.

Recommended Answers

All 3 Replies

Member Avatar for JorgeM

I think you are on the right track. Of course, there is nothing like having the experience, but you mentioned that this is entry level, so the only expectation really should be is understanding the concepts.

Aside from reading, you should definately build some examples using the various technologies you mentioned.

I would definately focus on HTML, CSS, JavaScript, Ajax, and jQuery.

then...depending on what they use for server-side, its probably going to be either PHP, JAVA, or ASP.NET.

Flash and photoshop come from field experience...unless you attended a technical school, most university classes dont dive into specific products like Adobe.

Member Avatar for Member #46692

First off, congratulations. It's great to land that kinda gig.

From a non technical point of view. Befriend everyone, and make sure you're making the right impressions. Come in early then stay late... Once everything has settled you can relax a little later on.

Second, experience is experience so there is little you can do to make up from something you read in a book or tutorial. It's like watching someone do a few reps in the gym. It counts for nothing unless you do the same.

That being said, practice after you go through your online tutorials is a good way to 'FAKE' your experience. I've never really had any formal programming training whatsover and mostly I've learned from sites such as this... Yet in spite of this, I feel confident.

So watch an online tutorial then try to put it into action somehow. As you work through it you will come across problems you need to solve. Being in a professional environment you will naturally learn to code to industry standards.

Try looking into code version control as well if you get a chance.

Member Avatar for bo0ga

thanks!

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.