000-Nobody

244: Rapidfire 80

01:09:10   Download

What’s the difference between a site that’s straight up files vs WordPress? What’s CSP and why does it matter? Does MySQL matter? Understanding the benefits of HTTP2. And how can you clean up a project you’re taking over?

Comment Bag

  • No comments were pulled out of the bag this episode.

Q & A

  • 13:18 Recently my company assigned me a new project in which i have to take a copy of older project. I find it really difficult to work on this project. If I make one change, layout breaks somewhere else. Is there a way I can make my life easier without resigning?
  • 23:30 When you guys make websites, do you host a set of pure code files or do you use WordPress, and if you use WordPress how do you go about learning it?
  • 33:30 So on a recent episode you touched on using Mozilla’s Observatory project to scan your site’s front-end for security issues. The first item on Observatory’s report card was the Content Security Policy. I’d love to get a passing grade on these item, but I don’t see a fast path to get there without serious reconsideration of my theme and plugins.
  • 42:30 Am I the only one who thinks despite H2 being on the horizon, nothing should change in terms of workflow? Have I misunderstood a fundamental aspect of H2? What do you guys think?
  • 51:28 What’s the best way to call large CSS or JS libraries like Twitter Bootstrap on your page?
  • 54:45 Is MySQL being phased out?

Links

ShopTalk Show Law Declarations

  • No ShopTalk Show Laws were declared during this episode.

Sponsor: Typekit 31:35

Typekit is the best way to get the fonts you need for all your creative projects. Designers have counted on us for years to serve beautiful type on the web, and Creative Cloud members continue to delight at learning how to sync fonts from Typekit to local applications. We’ve now expanded our offering substantially with Typekit Marketplace, which uses the same font sync and web hosting technologies to deliver an even broader range of fonts, with prices set by participating foundries. We’re excited to see what you make with this.

Browse the Marketplace and get ideas.

Sponsor: Indeed Prime 50:26

Indeed Prime helps tech talent such as software developers land their dream job. Candidates get immediate exposure to the best tech companies with just one simple application. Companies on Prime’s exclusive platform message candidates with salary upfront. The average software developer gets 5 employer contacts and an average salary offer of $125,000. Indeed Prime is 100% free for candidates — no strings attached. And when you’re hired, Indeed Prime gives you a $2,000 bonus to say thanks for using Prime. Sign up now.

Job Mention

  • Alex Zaworski

    What is the benefit of a CSP that allows unsafe inline? That’s so confusing to me. Is it just to tick a box on Observatory (et al) saying “yup I did the CSP thing!” or what? Does it still protect you from anything?

  • Here is what I would say to Prakesh (apologies if I spelled that incorrectly):

    There are two very important things to remember:
    1. Your company needs to make money. You need to make money. You were hired to complete a task that makes more money for the company than it does for you. Remember that first.
    2. Your situation is web development IRL. There is ALWAYS legacy code. Prove yourself first, and earn those “brand-new” projects (w/o compromising your salary).

    Here’s how you cope:
    1. SHIP FIRST. Finish the first project as fast as you possibly can, proving to your boss that you are actually capable of completing the task they hired you to complete. A LOT of developers are a combination of ego and enthusiasm, and always believe that they could write that code better. Many, in my experience, can’t actually deliver on it, though.
    2. During this first project, do these things:
    1. make notes where spaghetti code introduces additional risk to completing the work and meeting the deadlines. keep a notebook handy, and when you encounter identifiable risk, open your notebook, write down the new line item, close the notebook, and get back to work.
    2. change a tiny bit of code every time you are in the code base. 3. give your boss a project retrospective after it ships, that outlines what you’ve identified as the issues.
    1. “the code is terrible” is not an acceptable answer.
    2. use it as an opportunity to show initiative (by writing up a project retrospective)

    Consider this approach to influencing permanent change:

    1. Take inventory of all the parts (write it down)
    2. Divide the parts up into these stages:
    1. What do I need to fix now, and what small improvement can I make today (like, add a unit test, or adding an assets folder, etc.)?
    2. What could I fix, but it would require a little more time to get it right?
    3. What needs to be scheduled deprecation (planned obsolescence) and re-written?
    3. Be faithful.
    1. Earn the reputation for honesty, transparency, and fortitude.
    2. Be kinder than you want to be, more communicative than you would be on your own.
    3. Cultivate compassion for your colleagues, and a healthy dose of self-awareness.
    4. Accommodate whenever possible, but don’t be afraid to be that brick wall when something is just plain wrong (use sparingly).

    Doing these things has helped me in my career as a programmer, and while I am not famous or rich, I’m still living quite comfortably and have not had to compromise the things that are deeply important to me, in order to do so.

    ^_^

  • David Hicken

    Here’s a good blog on the do’s and don’ts related to transitioning from HTTP/1.1 to HTTP/2: https://blog.cloudflare.com/http-2-for-web-developers