neil / tags / html

Tagged with “html” (4)

  1. Sticking to the essentials, with Sara Soueidan | Fixate

    Published Nov 16, 2017

    Sara is a freelance front-end web developer, author, and speaker from Lebanon. She was named Developer of the Year in the 2015 .net magazine awards, and awarded a Web Platform Award from O’Reilly. Sara is the author of Codrops CSS Reference, and is the co-author of Real-Life Responsive Web Design, which focuses on smart “responsive” workflows, effective UX patterns, and powerful front-end techniques.

    Time Stamped Show Notes

    2:33 – Sara is passionate about the possibilities developers have to build useful things for people and for the generations to come. She believes developers have the tools for building the future, and is excited by the fact that the web is getting more powerful by the day.

    3:21 – Sara says that learning and teaching have opened a lot of doors for her. She first got into speaking because of the articles she wrote whilst experimenting with, and learning new features. She actually got her first job from her experiments on CodePen.

    4:34 – Burning out after working on a project taught Sara about what to do, what not to do, what to expect, what not to expect, and to tell clients what to expect and what not to expect.

    8:16 – Sara explains that she doesn’t use a lot of frameworks or tools. She uses HTML, CSS, and Sass. On very simple projects, she doesn’t even use Grunt, Gulp, or any other build tool like that. She writes with the bare minimum.

    9:00 – Sara uses Alfred to speed up her workflow.

    9:37 – TextExpander helps Sara save time by allowing her to respond to frequently asked questions in emails she receives using templates.

    10:17 – Sara loves Sublime Text as her editor, and uses a lot of the plugins that come with it to help her type less.

    10:52 – Sara works early in the morning to avoid distractions on Twitter.

    11:27 – Sara removes any applications, such as email and Twitter, from her work computer that are not essential for work.

    13:05 – Larry mentions how Dash is an app that aggregates documentation, and also integrates nicely with Alfred. It also has its own snippet manager, similar to TextExpander.

    13:56 – Sara finds that she doesn’t have the most productive way to set up projects. She currently uses Jekyll for her website, but the bigger the website becomes, the slower Jekyll becomes.

    14:30 – She admits that Grunt, Gulp, Browserify, or Webpack would make her workflow better, but she finds the thought of installing them and getting them to work overwhelming.

    15:42 – Sara is excited about CSS Grid, because it’s like a CSS framework without a framework. She believes that there’ll be no need for any kind of CSS framework to build grids and websites in the future. She mentions that she has never been a fan of frameworks like Bootstrap as she feels there’s always too much to edit, change, and fix.

    16:21 – Combining CSS Grid with Flexbox is “like magic”.

    17:23 – Sara makes time to learn new things when she needs to use new things.

    18:48 – “Java is to JavaScript as car is to carpet.” Sara studied Java in university. Learning that there was a fundamental difference between Java and Javascript, and that there was a mental shift required in order to work in the different languages has changed the way Sara views technologies.

    Quickfire Questions

    20:17 – Best advice about programming

    Learn the basics. Learn HTML, CSS, and native JavaScript before rushing into frameworks. Learn what you need, when you need it.

    20:46 – Habits for writing better code

    Thinking from a user’s perspective, not only a developer’s perspective. Test components early on – not code testing, but user testing.

    21:39 – BookResponsive Design: Patterns & Principles by Ethan MarcotteGoing Responsive by Karen McGraneAdaptive Web Design by Aaron GustafsonInclusive Design Patterns by Heydon Pickering

    22:50 – Inspiring devsEthan Marcotte and Jeremy Keith. Sara is inspired by anyone who works for the user and who teaches people in the industry to care about them too. She likes that these two authors teach developers how to write better experiences.

    24:40 – How to learn code from scratch

    Sara says that she would definitely be overwhelmed at first if she had to learn programming from scratch. She mentions that she is thankful that she had a mentor to help her get started from the right place. She would start with the basics, because she can’t use a tool or a language unless she really understands it.

    25:34 – How to work smart

    Work healthy. Take care of yourself and to get enough sleep. A healthy body is a healthy mind.

    Books, Tools, and Tech Mentioned

    CoDrops CSS Reference

    CodePen

    Sass

    CodeKit

    Alfred App

    Dash

    TextExpander

    Jekyll

    Sublime Text

    Browserify

    WebPack

    The Smashing Book 5: Real-Life Responsive Web Design

    Contact Sara

    twitter: @SaraSoueidan

    website: www.sarasoueidan.com

    http://fixate.it/podcast/sticking-to-the-essentials-sara-soueidan/

    —Huffduffed by neil

  2. Predicting the future with Rachel Andrew, Eric Meyer, and Jeffrey Zeldman | The Web Ahead

    The landscape of what’s possible in web page layout is changing. Jen has a theory that this change will be a big one — perhaps the biggest change to graphic design on the web in over 15 years. Rachel, Jeffrey, and Eric join her to debate if that’s true or not, and to surmise what the future might bring. This special episode was recorded live at An Event Apart Nashville.

    http://www.thewebahead.net/115

    —Huffduffed by neil

  3. Making Sense of A Mess with Abby Covert | The Web Ahead

    From a best practice standpoint, looking at the stuff that they have. Generally that’s a lot of things. A typical company for me won’t be that large in employee size, but it might have 25 different properties. From the logged in versus logged out standpoint of what their employees use, what their partners use, and what their users or consumers use.

    Looking at all of those things heuristically and really understanding what they have. Generally I am the first person to make a picture of all of those things together. That’s a big part of what I do.

    I spend a lot of time working with internal employees to understand what they have and how it got to the point that it’s at. Also how big it is. And I like to talk about how much it hurts. [Laughs] Because at a certain moment, I have to help prioritize, "Alright, well, everything is red. How red is it?" In terms of figuring out whose stuff gets fixed first, or what we restructure first, or who comes on a platform first, or who serves as a beta team. Things like that.

    That upfront stakeholder and internal research to get to that picture of where they’re at can take days, it could take weeks. I’ve had it take months, depending on the size of the project and company. From there, it’s really about architecting a series of experiences for those people that are going to be working with the decision-making of what we’re going to be making to experience the user as much as possible.

    Whether that involves going out and getting research done, or doing research myself, or referencing research that’s been done. In larger organizations, there’s generally an ongoing research department that you can tap in to and ask to do custom things for you, or reference things they’ve done for other initiatives.

    Taking that research and formulating it into objects that can be used in a workshop to make those stakeholders and designers and business people and technologists understand who this person is, in a way that’s respectful of their time and decision-making abilities. Generally trying to get that into a couple days over a couple weeks, or a couple weeks over a couple months, depending on the size of the project.

    In those workshops, we’re really getting at the crux of where the language of our users and where the language of the business may not be in agreement. A lot of that comes down to having conversations about, like, "What is our actual goal here? Are we looking at this as, we’re trying to be seen as an authority?" Because, in that case, you do want to take a different language, potentially, than your users. It still has to be one that they understand, but it might still be able to be authoritative and be your language, as opposed to using theirs. If it’s something that you want to make them feel like they’re part of a community, you’re probably going to want to have it written more in their language and designed more in their aesthetic.

    Getting into those kinds of conversations and preparing people for the idea that they’re going to have to make concessions with the decisions that are going to be made. That it’s not going to be, whoever is higher up in the hierarchy of the org chart is going to get to make the decision. That’s generally a structure that does make for unhappy designers and technologists and business people and, ultimately, I think, executives as well.

    Once the workshop part of my job is coming to its completion, at that point, teams are generally set out to do actions of their own. There are a lot of next steps and parking lot items that come out of meetings like that. A lot of next workshop steps, in terms of smaller workshops that they want to have with their own teams to make critical decisions. But while they’re doing that, I’m generally making some level of record of the consensus that we came to. That generally comes in the form of a map or large set of maps, depending on the context of the assignment.

    That’s pretty much start to finish what we’re dealing with.

    http://thewebahead.net/92

    —Huffduffed by neil