Online Marketing

Janice Hall: Farmers Market Operating Guidelines During COVID-19 Outbreak

These are based on the Potential risks associated with COVID-19 also Known as the coronavirus and its impact on the Health and the economic well-being of our farmers, The next few segments will Provide refresher practices and give you some enhanced best practices to have in place to protect You and your customers Now, let’s look at some Ways that you can protect yourself and your customers, Farmers, vendors and Market staff should wear food-grade, gloves and Change them frequently as soon as they become Soiled or contaminated Make sure that you are washing your hands before putting on a new pair of gloves.

Next, you should increase the number of hand-washing stations. For customers and vendors, and also remember to post Signs reminding everyone to wash their hands The picture on this slide. Shows you an example of a hand-washing station that You can make yourself at home if you don’t have access to one. Each farmer should have Soap, paper towels and hand wipes such as Wet Ones and hand sanitizers for their booth.

Now there is a difference between hand, wipes and disinfectant wipes. Please note that disinfectant wipes such as Clorox or Lysol Wipes should not be used on your hands or any surface that will come in contact with the food. Please read the label to make sure that you’re following instructions for proper and safe use. You want to make sure that You limit the customers from handling the produce. One good way to do this is to have all of your foods pre-packaged To slow down the spread of This virus and other bacteria limit the customers from Touching the product, All foods should be pre-packaged to eliminate potential Contamination at the market Examples would be pre-packing.

Breads and baked goods Pre-packing all foods, Will help in this effort Now how your booth is Stocked and positioned can make a big difference. In you doing your part to keep things safe, Let’s take a look at your Farmers market booth is yours, ready Institute six to 10 feet of space between vendor booths, where possible. Now, if you’re unsure about How much space this is, you can simply stretch Your arms side to side like an airplane or you Can do six to 10 paces or footsteps toe to toe The virus? Has minimum Ability to spread in the air It goes into the air and it Settles onto the surfaces You can also separate, but Don’t cross-contaminate Separate the duties at your booth, which means the person handling the money should be separate from the Person handling the produce.

You want to try to segregate the duties behind the market table so that the virus does not spread through currency. It is a good idea to Designate one individual to handle the money, tokens and coupons while others are handling The produce being sold Again, wear food-grade, gloves and change those gloves frequently So we’ve been hearing about practice social distancing with the coronavirus, but how does that apply? To a farmers market: Well, we need to limit bare hand, contact no shaking hands and no hugs Handshakes, hugs and close distancing, while talking to each other Is a part of our culture, however, to prevent the Spread of this virus, we will have to practice Social distancing So limit your handshakes and hugs, because if someone carrying the virus has virus particles on their hands, they can transfer that to Your hands by direct contact, So please, let’s show those appreciation gestures at a distance, A nice warm smile can go a long way.

It is critical that health and wellness is practiced at all costs, so protect your health and others by following these guidelines, Farmers and vendors, who are ill or showing signs of Illness should stay home. Incubation of this virus is up to 14 days, so it is quite possible. That you may have it spread it without, even knowing it Send a replacement to sell if you’re sick. If anyone within the farm business has been confirmed with COVID-19, notify the manager and remain home, Farmers should be readful.

Also of signs of ill customers, removing all products, They may have touched from their sales table. Do not remove them with your bare hands. It is important to postpone Those yummy samples, Like I mentioned, doing, This will reduce the risk of the virus particles transferring from one surface and person to another And lastly, as usual, no dogs Are allowed at the market? No dogs are allowed at the farmers market unless they are service.

Dogs, as defined as follows: Under the ADA, a service Dog is defined as a dog that will have that has Been individually trained to do work or perform tasks for an individual with a disability, The task or tasks performed by the dog must be directly related. To the person’s disability, Emotional support dogs do not qualify. So to sum this up best Practices is the key to healthy food and healthy customers For more information on the farmers market operating guidelines during The COVID-19 outbreak you can visit the Farmers Market Authority At www.

Fma.Alabama.Gov or the Alabama Cooperative Extension System at http://www.Aces.Edu. Thank you.


Online Marketing

Web Publishing Tutorial: Creating a Custom Grid File

So we can implement a grid system. We’re going to assume we’re using the 960 grid system which comes in 12 and 14 column variations, and it defines 940 pixels of content 940 pixels wide with 10 pixels of gutter on either side of the design now for demonstration purposes will focus in on a 12 Column grid system, but to use a 16 column, we just need to use slightly different values when we set up our guidelines, remember with any grid system online, we’re focused in particular on columns on the vertical lines.

We always want to apply more control and more precision to how our widths are set up than our heights and that’s a main reason for that to get started here. We’re going to go ahead and create our first guideline and we’re going to use those guidelines down the road to guide us as we create boxes and shapes that represent our wire frames. Now, in order to do this, we need to use the rulers in Photoshop and, if you’re looking around – and you don’t see rulers in your version, it may be that you don’t have them active and so to turn them on.

You need to simply tap the command. Our key combination or control our if you’re on a pc, i’m going to do that now and you’ll, see that actually I lose my rulers because they’re already on but command R or ctrl R is a toggle combination. So I just tap it again, and that brings my rulers back now. The other issue that may come up is, we have here a 1200 pixel wide document, its 2,400 pixels tall, and you may have a similar document but you’re looking at your ruler, values and they’re.

Just not matching up now in this case they are. Maybe your values are a lot smaller, though what could be happening is even though you’ve created a document in pixels, your rulers are still up to measure things in inches and any time we’re doing web design. Everything’s a lot easier if we switch everything over to pixels. So in order to do that, all you need to do is tap the command, K or control k.

Key combination: that’s going to open up the global preferences window for photoshop and we’re actually going to scroll down here to the units and rulers subsection and we’re going to check out the units values. Now, I’m all set, my rulers are set to pixels. You can see here, though there are a number of different possibilities and type as well is set to pixels and i’m going to leave both those values.

Just as is so i’ll cancel out of here. Okay with my values, confirmed with my rulers, set up, I’m ready to go ahead and create my first guideline, so I’m going to move my tool set over here on the left a little bit over to get it out of the way, and now I can click And drag from my rulers over on to my document and i’m just going to hold down my mouse or my left trackpad button as I do this and then move this right over onto the document as soon as I release there.

I have my guideline now. If I’m not happy with the placement, I can always move a guideline after I’ve created it. In order to do that, I want to make sure i’m using the move tool which, in my tool palette here, is the very first one. So I can either click on it or I can use the keyboard shortcut v to select the move tool and now I can easily move things around, including my guidelines. So if I hover over this you’ll notice, the cursor changes indicating I can move it left or right and then I can click and drag it in either of those directions.

Now you’ll notice, as I move this guideline, that a little window pops up showing me my exact pixel value for that particular location, that’s a really handy indicator and unfortunately it’s limited to cs6. So if you have an earlier version of Photoshop, you won’t be seeing that value. What you’ll notice, in either case, though, is as I move this even if I’m very careful I’m jumping ahead by four five pixels every time I move my cursor and that’s not very good for the kind of precision work we’re trying to do now, so an easy Way to get more control more precision over what’s happening is to zoom in on the document, and I’m going to tap the Z key to move over to my magnifying glass and because I’m in Photoshop cs6 I’m going to actually click and then drag over here.

Whoop click and drag the other way, and that’s going to allow me to zoom in on the area. If you have an earlier version of Photoshop, you can actually just go to the zoom tool, either click and drag a square over the area that you want to focus on or just keep pressing the mouse button or the left track pad button over the area. You want to zoom in on so now that I’m zoomed in I’m going to just scroll over a little ways here and I’m going to hit V to move back to my move tool.

And now, as I move my guideline left and right you’ll see. Not only can I move it to the nearest pixel, but I’m actually ending up with some decimal values here as well. That’s a little bit frustrating too, because I want to stick to pixels well an easy way to not only stick to integer values, whole integer values, but also to get a little more control over my movement is to hold down the shift key as I do this.

What that’ll do is snap the guideline to the different hash marks on my ruler here so, for example, between 300 and 350, I have four different hash marks, so that means, if I hold down shift, I can go from 300 to 310 to 3. 20. 30. 40. All the way over 250, so down to the nearest 10 pixels, I can move this left and right, which is exactly the kind of control I want for what I’m doing. So. If I wanted to create another guideline, all I do is come back to my ruler.

Click and drag it over and I have my second guideline now the trick is: where do I actually put these guys? Well, I want them in very particular places based both on the 960 grid system. I am based on the fact that I have a document here. That’s 1200 pixels wide well to help us out. I’ve created a document and you can actually download this from the course site in lore. Let’s go ahead and open that up for a second here, so we can see where it is so.

I’m inside of war and web publishing, I’m going to go over to resources to grab this document and it’s the guide placement for 12 and 16 column, 960 grids, so I’ll click on that and I’ll click to download. It’s like I’ve already grabbed it a couple times and I’ll pop it up here. So what this document gives us is the pixel values that we want to use for each one of our guidelines and each line in the document represents a different column, and so we need to guidelines for each column.

In this case, the left guideline is going to be at 130, the right guideline at 192, 10 to 70 and so on all the way down. If I wanted to use a 16 column grid, I would just use the values listed under there. I went ahead and printed this document out, so I have it at the ready and just remember it’s not only assuming a 960 grid, but it’s also assuming a 1200 pixel wide document, and so that’s going to mean that all of our guidelines are going to be Lined up just right so that our web page is centered on this 1200 pixel document.

Let’s come back into Photoshop in fine tune, the ones we’ve already created here. We know we want our first one to go to 1 30, so I’ll hold down shift and move this on down down to 130, and I know I want my second one at nine or 190, rather so I’ll move that to 190. My third one is going to be 2 to 10, so i’ll click and drag hold down shift that snaps to my hash marks on the ruler move that to 210, and my next one is going to be at 270, so i’ll jump over to 270.

Ok, I could keep going just like this and create all my guidelines. Show you one more way to do this, though, that’s available in all the recent versions of Photoshop, and it may be a little faster, especially for those of you using older versions who don’t have the benefit of the little display that pops up and shows me. My exact pixel value as I drag so it turns out. We can create these guidelines using the menu and we do that by going to view up in the menu area here at the top, and we come down to new guide and it’s going to give us two options.

Basically, we can choose the orientation. Remember we’re sticking with vertical, so that’s good and then we simply provide the position value. So I’ve created my first four guides. I know my fifth one has got to be at let’s see here to 90, so i’ll type in 290 and hit ok and there’s my guide so back up to view down to new guide and I’ve created 290. So 350 comes next punch that in and there’s my next guide.

Well, there’s always a way to do things faster and it turns out. Even this can be sped up a little bit by using a keyboard shortcut, and this is actually a good trick to know any time you want to speed up something that doesn’t already have a keyboard shortcut available. This is a really great flexible way in Photoshop to customize the interface so you’ll notice. If I come to view new guide, does not have a keyboard shortcut set up for it, and I know that because to the right here, there’s no key combination as you’ll notice.

On some of these others like, if I wanted to see extras, I can do command H and, as we saw earlier, rulers our command are well. I have no keyboard shortcut for new guide, but that doesn’t mean I can’t set one up and in order to do that, all I need to do is come over to the Edit menu and then come down to keyboard shortcuts from here I can choose my different Menus and I’m going to go back over to view because that’s where the command, I’m looking for libs and I’m going to scroll down and there’s so many different things that can be mapped to keyboard shortcuts.

But I’m going to come all the way down to new guide there. It is and to provide my shortcut. All I need to do is literally click in here and then type the shortcut literally type, the shortcut that I want to use for this particular command. Now the trick with this is because there are so many shortcuts already set up. It can be tricky to find one. That’s not in use now, I’m pretty sure if I do command shift one that that is a available shortcut.

So let me try that command shift. One: okay and if you’re on a PC you can do ctrl shift one to do that as well. I’ll do command shift one. I got no warning telling me that it was taken, but you’ll notice. If I get rid of that and do say command R, which we know is taken now I get a warning saying it’s actually going to replace that old command. So I don’t want to do that so I’ll undo that and again we’ll do command shift.

One control shift: one is a possibility, if you’re on a PC, although frankly you could make this anything. You want just make sure you remember how you’ve set up your shortcut, so you can easily get back to them. Okay, command shift one and will enter in there to save that, and then click. Ok, now that we’re back in our document, we can command shift one, and lo and behold our new guy dialog box opens up.

We can set the position we just did 350. So now we’ll do 370 and we hit enter and there’s our guide command shift. One to create another guide will do 430 and we’ll just go through a couple of these, so you can see how fast this process really can get. And again I printed out the document with the ruler values or the guide values I should say so. I have that right beside me here to speed this up and i’ll do one more okay, so once everything is done, we can zoom back out and we’ll have ourselves the makings of a really good wireframe document with our 12 different columns or if you wanted to You could use a 16 column grid, no problem right about this time.

It’s probably a good idea to save the document, save all that hard work that we’ve put in here and in a follow-up lesson, we’ll talk more about actually creating wireframes and we’ll see you then


Online Marketing

dotCSS 2014 – Harry Roberts – 10 Principles for effective Front-end Development

Now I know this is um dot CSS. So I should really be talking about some hardcore sass, or maybe some really intricate CSS architecture. But one thing I’ve learned is that it’s really important every now and again to just leave our tool to learn, step back and take a much broader view of what we do.

So that’s why I’m speaking about these principles, they’re personal principles of mine – these are things that I do when I work and every bit of work I do, regardless of the technology, the stack, the tools I use tries to follow these principles. They’re very new. I’ve never shared these before. So if it interested to see what people think, but that’s I kind of that’s kind of thing, I’m going for today, less about tooling more about approaches so yeah, my name is Harry.

I’m a consultant web developer. That means that I spend a lot of time with a lot of different clients. I travel around a lot and learn about everybody’s problems. I’m like a developer therapist in doing this. I’ve realized that it doesn’t matter what stacks our company uses. It doesn’t matter what which preprocessor they’re used. They always have similar problems that can’t always be solved by specifics, and it’s really important to know specifics.

It’s good to know, flexbox why it’s valuable to know about SAS, it’s very, very valuable, to know different technologies, but specifics aren’t always that transferrable. One thing I’ve learned in the last few years, especially working for myself as a consultant, is that code is actually only a tiny, tiny part of what we do think about what you do. In your your day to day life, you might deal with clients, you might spend a lot of time discussing compromises with designers.

You might spend a lot of time explaining why things can’t be done to project managers. The actual code you write is a tiny, tiny part of your drug, so I think it’s important to realize that you know focuses, should shift and mind shifted a few years ago and much much for the better. I found that on a more effective developer, by ignoring the specifics and trying to focus on principle LED approach to development.

The interest is now anyone’s thoughts on this. So if you want to tweet during this talk, I’d be really grateful, so I’ve just 10 CSS will do. I know it says you know, principles for front-end development, but I only really write CSS. So all of these principles I applied directly to CSS start off with an easy one. The simplest option is usually the best. I got Hugo who’s speaking a little later to do some translations.

For me, if they’re wrong, it’s his fault, the simplest doctrine is usually the best. This seems quite obvious right. Let’s start with an obvious one. The simple option is probably the cheapest to implement the quickest and cheapest option to implement will be the simplest one. This is good for business and we’ll talk about business in a second that’s another one of my principles, but quick and cheap to implement is really valuable and it’s also easy for other developers to inherit.

When you pick up a system from someone, it’s really complex and over-engineer, that’s a horrible thing to try and work with, so always err on the side of simplicity. If you’ve got two or more options, two or more solutions to a problem, all let’s try and pick the simplest, it’s less likely to break it’s probably more robust. It’s just locks easier to work with also lessens the amount of cognitive overhead when working with a system.

It’s a really horrible thing to have to try and remember every moving part in a system which leads men to the next bit, always try and reduce the amount of moving parts in a system as a developer. It’s very easy just to do as you’re told, or it’s very easy to build the features that have been requested. I think it’s really valuable to say no to a lot of things. The best code is no occurred at all, so it’s a really good exercise for developers to get rid of unnecessary stuff.

Anything that could be removed from a project try and get rid that could be features in. I could be telling a client that you know we don’t really need this feature, let’s get rid of it or it could be actual lines of CSS. It could be reducing a 20 line mixing down into a single helper class right. Removing the amount of moving parts is a really valuable exercise. Every moving part in a system is a potential thing to go wrong.

It’s a potential point of failure. Everything you add to a system introduces the risk of something going wrong. It’s easier to men attained a system with fewer moving parts. I think it’s a really valuable exercise to get rid. The third principle understand the business now. In this context, the business could mean a few things. If you work for an agency, the business would be your managers and the client the person funding the project.

If you work in honks, if you work for a starter for a product like Kayla, get the financial times, the business is where you work every day, you’re surrounded by the business understand the business makes you a very valuable developer. It’s important to understand that every bit of work you do has a cost and a value associated with it. Try and understand the financials. I don’t mean you know, learning what your colleagues salary is, but perhaps knowing what the company charges you out on for a day right.

It makes you much more effective understanding. The cost and value of your work means that you can make very very informed decisions about what you do for the good of the company. Don’t waste other people’s money. I like to also make you a much more valuable developer. Imagine a company looks like this and you’re just a developer, you’re, not better than anyone else, you’re, no cleverer, no more important anyone else and unfortunately you’re, probably quite replaceable.

If you look around you right now, there are hundreds of people in this room who all do similar jobs so being a regular developer. Who just does their bit of the the task, isn’t necessarily a very valuable developer to have. It sounds really cruel, but I do believe it’s true um, so, instead of having this position within a business, try and have this position trying to connect yourself with everyone else’s problems, understand the cost and the value of your work.

It makes you much more valuable principle. Number four care, laughs and care appropriately. Another thing I learned in especially my time working in big companies. No one cares about your kurd more than you do. Your client doesn’t care if you’ve used SAS or less the business doesn’t really care. If you used an inline style or not, don’t stress too much about your own work and pick the right battles for everybody else, there are a lot more people working on that team than just you.

When you have. Whenever you have discussions, you have to balance everybody else’s needs and wants remain objective. When you do this care less about your own work and care about the good of the team, the stakeholders there’s a much bigger picture out there. The bigger picture looks something like this: we have the user, the person who needs the product you’re building the team. That would be you and your colleagues, designers developers, your solutions, architects, UX guys and then there’s the business.

The person funding this project. Now I’ve worked with a lot of developers who think in this degree they think about the team. They make decisions for the team. They want to use a preprocessor, because this is one we want to use good developers a bit like jugglers. Good developers will think here. The overlap, but great developers think about everybody else’s overlap. Great developers are very unselfish people, and I’ve found this in working with different companies that the most productive teams are the people who make sacrifices themselves for the good of everybody else, so care less about your own work and care more appropriately about everybody else.

The fifth of the ten principles – pragmatism, Trump’s perfection – it’s better to have good enough working today than it is to wait for perper for perfection tomorrow, get things alive. You’ve always got time to make things better. Perfect is a real real sort of misfire on the web. Anyway, think about all the different browsers devices network connections, we will never achieve perfect, so it’s not there’s no point even trying.

I worked with a client who delayed a release by nearly two weeks, because the color of the nav highlight was wrong. That’s insane! That’s! That is a you know, that is a very soft edge case thing to happen, but that’s expensive missing out on potentially two weeks of new signups, because the nav was slightly the wrong. Color is expensive users, don’t care if they’re now slightly the wrong color, because they never saw the PS DS, pragmatism, Trump’s perfection, something hacky that works today is better than something perfect that might work next week.

Never hold yourself back in the pursuit of perfection because it just slows teams down thinker, product level right. Some of these principles seem fairly interconnected. So this is a little like think about the business, but thinking up product levels, a really valuable thing for a developer. To do there’s a very sort of old but harmful view that as CSS developers, it’s our job to build PS, DS and that’s really harmful, because that’s not true at all.

We’ve got to think about the performance of occurred base. We need to think about the maintainability. The velocity of the team we’ve got a lot more to worry about than we realize so try not to put yourself in a bubble and figure out the entire product you’re in a very, very valuable position if you’ve started understanding the business and you’re a developer. So you understand the technology, you can make great decisions for that product.

True story. I once worked a company where a simple UI decision that I made save that company hundreds of thousands of pounds – it’s too long, a story to get into now, but you want to hear it over a beer I’ll. Let you buy me a beer, but yet we’ve got a profound ability to, in fact affect not in fact affect entire product. Use that wisely do what’s right for everyone. Seven do not design systems around edge cases.

I encounter this one quite a lot. Basically, don’t let the minority lead, the majority do not bet your entire product around statistical outliers or another example. For you, I worked with a company that was making a mobile website a mobile web app. They needed a spinner right, a little loading spinner. Now we had to accommodate a really old flavor of Android and a really old flavor of blackberry.

Now the Android didn’t support CSS animations and the BlackBerry didn’t support CSS and CSS animations or animated gifs, so the team spent nearly a month building a spinner that worked in every single browser. It was a combination of sprites, some horrible JavaScript and its really clunky and a really bad rendering performance, and this spinner went out to a hundred percent of our users. So, even though I only needed to be given to a small fraction of a percentage, this spinner went out to everyone.

Designing systems around edge cases is a really expensive thing to it can hold the quality of the product back solve every edge case as an edge case. Don’t let it leak in and influence the entire build of a system number eight another. Quite specific one. Don’t make decisions based on anecdotal evidence, another true story: I worked with a company who they really should have been using a preprocessor.

They had a big, a big UI and it would have really benefited from using SAS, and I got that I asked them. How can we don’t use SAS and the response was? Oh someone told me that variables don’t work very well in SAS. Well, of course, they do. Tens of thousands of people use sat every day, of course, variables working SAS. Did you not think to try this out yourself and they hadn’t they hadn’t fought to run their own tests.

They trusted a story. They trusted some box. I never trust stories, always trusted data. It’s very expensive to ignore the numbers. Another example you’re going out to eat a restaurant and you find a hundred five-star reviews for this place, and then you see one two-star review. You will obviously ignore that two-star review. The two-star review is a statistical outlier, get rid of anomalies, always trust numbers try and avoid trusting anecdotes and stories.

The ninth principle don’t build it until you’ve been asked for it. It’s really tempting, especially as a CSS developer, I’m speaking personally here to over-deliver. It’s really cool to say: I’ve made this mix in which does this, but if you pass in this parameter it does this. The problem is no one’s asked for that. So I’ve spent the business as money. I’ve made something that I haven’t paid for. I’ve spent an extra half day, sugarcoating some some sass, no one’s asked for that, but someone’s paid for it right.

So it’s a rephrasing of yeah. You ain’t going to need it. The the programming software engineering principle and it’s really valuable to try and follow it, can be harmful because you have the cost of the initial work upfront. If someone hasn’t asked for a feature, don’t build it because you’re spending someone else’s money, but also it can influence the rest of an entire project. If you build something now that has a certain dependency on a third-party library, your product is now hooked into that dependency.

So it might have a knock-on effect with future features. You want to add um and yet maintaining things that no one even wanted. Imagine having to tell your manager that I had to bug fix something, or what did you have to bug fix? You don’t really know about it, cuz, no one asked for it, but I built it anyway, and I’ve spent two days fixing it it’s a very unwise, irresponsible approach to building websites don’t build anything until you’ve been asked for it solve every single problem.

Only when you encounter it, you might be well aware that you need to support international ization in six months time. Do it in six months time, don’t do any work ahead of time expect and accommodate change. If this is the one thing that any sort of large-scale site developer should always try and do expect and accommodate change, I’ve been doing this long enough to know that clients will throw you a curve ball.

The business will make unusual decisions. Users will request odd features. Everything is subject to change, so expect it and accommodate it. Every bit of code you write, make sure you can undo it next. You can reverse decisions, keep yourself free to change direction, never tie yourself down, never put yourself into a corner. You can’t out of everything. Is subject to change so at least accommodate that, and you can use this as a really good way to just lessen the stress.

I get a lot of workshop attendees asking me: oh, we really struggle to find the right name for something. You know we spend a lot of time thing about the right name for something my advice is always pick something now right worry about something that fixes a problem right now, because they’ll probably change anyway, don’t try and predict the future always make make sure that you Can change direction, undo things and modify decisions that were made months ago because you’ll thank yourself in the long run? So just a recap, my ten principles, my 10 personal principles for effective front-end development, pick the simplest option.

It’s the quickest and the cheapest to implement it’s the easiest one to maintain its own, that’s least likely to go wrong. No one appreciates over-engineered kurd a website is not the place to show off, reduce the amount of moving parts, remove the amount of moving part from a system so that it’s more robust, more things going on in a system means more things that could potentially go wrong. It’s a really good exercise to develop as a developer, to build less.

The best code is no code at all. It’s the fastest. It’s the most robust. It’s the easiest to debug. Understand the business be aware of the fact that everything you do has a cost and a value associated with it be responsible with other people’s money. It makes you a better developer in terms of actually writing CSS, but it also makes you more employable more valuable. Member of the team, if it can be less selfish and spend your employees money wisely, you will get more effective products off the back of it and they will appreciate that work, care less and care appropriately.

When no one cares about your CSS more than you do. Stop being enclosed in a bubble and think about what you can do for everybody, pragmatism, Trump’s perfection, don’t be the guy who holds back, or at least for nearly two weeks, because the nav is slightly wrong. It’s expensive! It’s unwise and it doesn’t help anyone hacking something together. That works today is better than having something perfect in three weeks time: thinker product-level, the knowledge you have of the product you work on allows you to make very profound and far-reaching long-lasting decisions.

Do not design systems around edge cases? Do not let the minority influence the majority of your product, always design solutions to edge cases as edge cases themselves. There’s no point weighing down the entire product to cater to a minority. Good example would be if five percent of your revenue comes from ie7 users do not spend twenty five percent of your time accommodating those users it doesn’t make any sense.

I don’t make decisions based on anecdotal evidence. Anecdotes are, by definition, edge cases. Their stories always trust data, don’t build it until you’ve been asked for it. It’s tempting to build cool things before anyone needs it, but that adds blur to the codebase. It could always go wrong. You might have to maintain that for the next two years solve every problem as and when you encounter it and finally expect under comedy change.

You know full well that clients make weird decisions. They will change their mind. The business can change, focus and direction every bit of CSS. You write every bit of code. You write should facilitate that. Never tie yourself now, never put yourself into a corner, and that is me saying. Thank you very much for listening.