skip to main content

Posts tagged “web”, page 5

  1. HTML, CSS and our vanishing industry entry points
    rachelandrew.co.uk

    Fighting words from Rachel Andrew, defending the ease of learning HTML and CSS from scratch:

    Whether front or backend, many of us without a computer science background are here because of the ease of starting to write HTML and CSS. The magic of seeing our code do stuff on a real live webpage!

    Yes! The instantaneous feedback when editing HTML or CSS on a live webpage is, to me, one of the most important characteristics of the web as a medium. Having no layers of abstraction between creative input and final output is one of the web’s miracles.

    I might be the “old guard” but if you think I’m incapable of learning React, or another framework, and am defending my way of working because of this, please get over yourself. However, 22 year old me would have looked at those things and run away. If we make it so that you have to understand programming to even start, then we take something open and enabling, and place it back in the hands of those who are already privileged. I have plenty of fight left in me to stand up against that.

    I couldn’t agree more. It really was the ease of getting started that got me into web development, and kept me away from native app development. Easy to learn, hard to master is a wonderful trait that the web should fight to keep.

  2. I’m a Web Designer
    andy-bell.design

    Still on the topic of web development job titles, Andy Bell hits the nail on the head. This paragraph describes my exact problem assigning a title to myself:

    I struggled with how to place myself when I went back to freelancing last year because I’m both a designer and a developer. I toyed with “Independent Designer & Developer” which worked out alright but did make me sound like a bit of a “Jack of all trades”. I’m also technically “Full Stack”, but I won’t use that as a title because in my head, a Full Stack Developer is a back-end developer who knows a bit of client-side JavaScript and CSS.

    I tried to avoid the issue altogether and go with a short description instead of a title — “design and code for the web” is what I ended up with. But when pressed for a title, I do fall back to “front-end web developer,” which feels lamer every time I say it.

    Andy suggests “web designer.” Despite the baggage, it does seem to fit the bill. I like it. I promptly added myself to Andy’s personalsit.es directory with that as my top tag.

  3. The Great Divide
    css-tricks.com

    Chris Coyier tries to make sense of what “front-end web developer” means now, and gets to the core of why I avoid calling myself one:

    When companies post job openings for “Front-End Developer,” what are they really asking for? Assuming they actually know (lolz), the title front-end developer alone isn’t doing enough. It’s likely more helpful to know which side of the divide they need the most.

    Two “front-end web developers” can be standing right next to each other and have little, if any, skill sets in common. That’s downright bizarre to me for a job title so specific and ubiquitous. I’m sure that’s already the case with a job title like designer, but front-end web developer is a niche within a niche already.

  4. How to Fix Social Media by Injecting A Chunk of the Blogosphere
    kottke.org

    Tim Carmody:

    Most of the proper publications I’ve written for, even the net-native ones, have been dense enough to hold an atmosphere.

    And guess what? So have Twitter and Facebook. Just by enduring, those places have become places for lasting connections and friendships and career opportunities, in a way the blogosphere never was, at least for me. (Maybe this is partly a function of timing, but look: I was there.) And this means that, despite their toxicity, despite their shortcomings, despite all the promises that have gone unfulfilled, Twitter and Facebook have continued to matter in a way that blogs don’t.

  5. Signal v Noise exits Medium
    m.signalvnoise.com

    David Heinemeier Hansson:

    Traditional blogs might have swung out of favor, as we all discovered the benefits of social media and aggregating platforms, but we think they’re about to swing back in style, as we all discover the real costs and problems brought by such centralization.

    Dave Rupert comments:

    Blogging is back, baby! Awooo!

    I’m definitely feeling the momentum. I’ve been acutely aware of it as I’ve worked on getting this blog up and running over the past year, and it’s only getting stronger.

  6. Line breaking - Florian Rivoal at dotCSS 2018
    dotconferences.com

    Florian goes over a set of confusingly named properties and values from the css-text-3 specification that control what happens to white spaces when laying out text, and how line breaking works. He explains the logic of the system, different ways the properties can be used to achieve various results, and looks into some of the complication caused by incomplete implementations.

    I care about this topic a lot, but it really tests my patience. If only browser support for these properties were consistent, I could start to build a mental model that takes them all into consideration. As it stands, it’s such a mess that I routinely have to spend time reading about it, and still not be super confident with the results.

  7. Evaluating Technology
    aneventapart.com

    Jeremy Keith:

    Now when we look at new things added to HMTL, new features, new browser APIs, what we tend to ask, of course, is: how well does it work?

    How well does this thing do what it claims it’s going to do? That’s an excellent question to ask whenever you’re evaluating a new technology or tool. But I don’t think it’s the most important question. I think it’s just as important to ask: how well does it fail?

    Nothing like a full hour of Jeremy Keith to get the year’s work started.

  8. We Should Replace Facebook With Personal Websites
    motherboard.vice.com

    Jason Koebler:

    There’s a subtext of the #deleteFacebook movement that has nothing to do with the company’s mishandling of personal data. It’s the idea that people who use Facebook are stupid, or shouldn’t have ever shared so much of their lives. But for people who came of age in the early 2000s, sharing our lives online is second nature, and largely came without consequences. There was no indication that something we’d been conditioned to do would be quickly weaponized against us.