Articles

It would be way too easy to answer this question with: “Whoever pays your bills.” And, honestly, I don’t think you can be a very successful web designer if you’re only driven by what the person paying you tells you to do.

Then again, that doesn’t mean you should swing to the exact opposite end and say that you only serve the end user.

When you take an extreme view or approach to this, you’re bound to leave someone or something important out. Everyone along the chain of command — your boss (if you work at an agency), your client, and their customers — matters.

So, what I’d suggest you do instead is approach the idea of who you really work for the way you would Maslow’s Hierarchy of Needs.

Establishing Your Own Hierarchy of Needs

Who do web designers really work for? I think the true answer to this question is: “Everyone.” But there’s a catch…

Think about some of the requests you’ve received from superiors, or clients in the past. How many times have you rolled your eyes at their wacky requests?

  • “The contact form would be better in the header so visitors can always see it.”
  • “Let’s use this stock photo of two women shaking hands that I’ve seen a few other companies use.”
  • “Why don’t we redesign all of this and make it look like this site my brother built last night?”

You’re the design professional. That’s why they’re paying you to design their website and they’re not doing it themselves. So, there comes a point where you have to push aside what they want for what they need. And this will ultimately help you figure out who you work for and what you actually owe them (because fulfilling every nitpicky and unreasonable request will never lead to anything good).

So, here’s where the Hierarchy of Needs comes in. If we’re creating our own, it would look like this to start:

Working for the Boss

According to Dr. Neel Burton on Psychology Today:

Maslow called the bottom… levels of the pyramid ‘deficiency needs’ because we do not feel anything if they are met but become anxious or distressed if they are not.

I’d argue that these basic needs are like the ones we fulfill for bosses (or clients, if you’re a freelancer and work for yourself). It would look something like this:

Of course, you’ll feel a sense of accomplishment by meeting these needs, but, as a creator, how important are these really to you? These are the basic things you have to do in order to make your boss happy and to stay gainfully employed. They also help to ensure that the client is happy with the boss and agency in the end.

Bottom line: Without these needs fulfilled, you won’t be able to move any deeper into the triangle/hierarchy. So, when focusing on working for your boss, make sure the basic needs are met so you can move on and serve others as they need you to.

Working for the Client

Now, if your boss and client are two different people, you’ll have a second layer of needs to attend to here.

Just as your boss wants you to help them make more money and earn a strong reputation within their space, so too does your client. However, the work you owe them is different. Here’s how it would be represented in the triangle:

Again, you’ll be pleased if you can do and be all these things that your client needs, but is this ultimately what drives you as a designer? Sure, you want to build great relationships with clients so they return to you time and time again with all their website and marketing needs. But in terms of being fulfilled by being a good listener or a timely communicator? Probably not.

All the same, it’s important to be skilled in this type of work and to know how to serve your clients in order to get to that top level. It’ll also help you prioritize their needs accordingly, so you’re not jumping at every single thing or request they claim to “need” and blowing the budget or scope of the job.

For example, if they start demanding more of you (like bombarding you with emails every day wanting to know what’s going on), you can confidently remind them that things are under control (because you’re adhering to the project deadlines, per your boss) and you’ve already scheduled the next client check-in for this week (because you’ve been a good communicator, just as they need you to be).

Working for the End User (Customer)

Maslow refers to the top-level of the pyramid as the growth need. And here’s how Dr. Burton sums this one up for us:

Once we have met our deficiency needs, the focus of our anxiety shifts to self-actualization, and we begin, even if only at a sub- or semi-conscious level, to contemplate our bigger picture. However, only a small minority of people are able to self-actualize because self-actualization calls upon uncommon qualities such as independence, awareness, creativity, originality, and, of course, courage.

These characteristics perfectly sum up everything you want to and should be as a web designer. Unfortunately, it’s those employer and client needs that can stand in your way before you can truly flex your muscles as a creative.

Once you’ve attended to the basics, though, you’ll get your chance to design the kinds of user experiences you know will delight your client’s customers.

Here’s how their part of the triangle should look:

These are universally applicable needs and cannot be ignored.

After you’ve addressed them, though, you will have fulfilled your responsibility to all three parties: your boss, your client, and your end users. And once you’ve done that, you are free to be the creative designer that you are.

Wrap-Up

What I want you to take away from this, is that there are certain basic needs which you must fulfill when working as a web designer. These are the ones you’ll put into your own hierarchy of needs.

Take a systematic approach, starting with your boss and ending with the customer:

  • What do you have to do to ensure that your boss is happy to have you on the team?
  • And that the client is pleased with the site you’ve built them?
  • So you can design a website and experience that end users respond to positively?

Once you’ve figured all this out, you’ll unlock the answer to whom you work for and, more importantly, how you should work for them.

 

Featured image via Pexels.

Source


Source de l’article sur Webdesignerdepot

The software industry has come a long journey and throughout this journey, Software Architecture has evolved a lot. Starting with 1-tier (Single-node), 2-tier (Client/ Server), 3-tier, and Distributed are some of the Software Architectural patterns we saw in this journey.

The Problem

The majority of software companies are moving from Monolithic architecture to Microservices architecture, and Microservices architecture is taking over the software industry day-by-day. While monolithic architecture has many benefits, it also has so many shortcomings when catering to modern software development needs. With those shortcomings of monolithic architecture, it is very difficult to meet the demand of the modern-world software requirements and as a result, microservices architecture is taking control of the software development aggressively. The Microservices architecture enables us to deploy our applications more frequently, independently, and reliably meeting modern-day software application development requirements.

Source de l’article sur DZONE

You’ve been working away at your latest design project, and the client has given the go-ahead on your lovingly created digital concepts. Now it’s time to bring those designs to life, and you have a developer queued up to do just that.

So your part’s done, right? Not quite. You’re going to want to make sure your developer has the best head start they can in order to create the site as you imagined.

Below are a few tips to make that handover process a little easier.

Communicate to Make It Great

Get Talking

Scheduling a face-to-face meeting with your developer to talk over your project’s specifics and ambitions will help align your expectations and make the intent behind your concepts more clear. It’s quite likely they’ll even ask questions and request assets you haven’t even thought of yet!

It’s not just a one-and-done thing either, your developer’s going to have questions or requirements that arise as the project progresses. Deciding on a communication channel to allow easy discussion will help you both immensely.

Annotating Your Concepts

Developers might seem like magicians with the way they bring your websites to life, but they’re not clairvoyant! Annotating your concepts where advanced functionality is required reduces ambiguity and makes it more likely that your cool, quirky idea is going to make it to production. If it’s a feature that’s particularly unusual, you might want to find an example of a website or code sandbox that does something similar.

An example of Figma’s comment tool in use to make developer notes.

Figma and Sketch both have comment functionality in order to make annotations a little easier, also allowing multiple parties to comment. If dealing with PDFs, there is also an annotation tool available through Adobe Acrobat.

Specify the Basics

The basis of modern front end development revolves around DRY thinking. Some might argue thinking about code can be pretty dry, but we’re not talking about that – in this case, DRY stands for Don’t Repeat Yourself.  Most developers will tackle a project by starting with defining variables: what colors, font sizes, grid columns… anything that can be reused! Good, consistent design follows this same principle – although it’s a habit that can be hard to get going at first.

Tip: It’s always easier to define variables if this mentality is approached towards the start of the project!  

Colors

Make a style guide that specifies the colors you’ve used in your designs. Think about their logical applications to help signpost how they might work as a variable – for example, what colors did you use for paragraph text, hyperlinks and backgrounds? Did you consider colors to convey status messaging, such as successes, warnings and errors?

Typefaces

Which fonts have you used for your project? Is there a consistent set of font sizes you used throughout? If you haven’t already, maybe consider a ratio-based type scale – I like to use ModularScale to help with this.

Basic HTML Elements

Think about general styling for these basic html tags:

  • Paragraphs <p>
  • Headings <h1–h6>
  • Bullet lists <ul> and numbered lists <ol>
  • Emphasized text <b>, <strong> and <em>

Buttons

How about buttons and links? What should they do when they’re hovered over, focused (using the tab key on a keyboard) or disabled?

Forms Fields and Inputs

What should form fields look like? Is there any validation checking that should occur when a form is submitted?  How about checkboxes and radio buttons?

It’s unlikely that you’re going to be able to cover absolutely every single eventuality – allow your developer to use some common sense to fill in the gaps, and be available to them if they have any questions. In the words of John Maxwell and your aunt’s home office wall sticker, teamwork makes the dream work.

Get Your Favic-on

Favicons are widely recognized as the small icon that appears to the left of the site title on your browser’s tab bar. Nowadays, the application of your site’s favicon is much further reaching, showing up in Google search results and app tiles. There’s also extra theming options available, such as the ability to customize the color of Google Chrome Android’s browser bar color for your site.

Using a generator site such as realfavicongenerator takes the pain out of much of this decision-making, allowing you to upload specific graphics as desired, creating silhouettes of your icon for Windows Metro tiles and macOS Safari pins, and packaging everything into easy-to-use files and code.

 Compress Your Images

Nobody wants to load a 20MB image when they’re on a slow connection or a data plan – it pays dividends to plan ahead and downsize your images so that they’re production-ready for the web. If you’re worried image compression is going to harm your image quality, fear not – you can go a long way with image compression before quality is seriously compromised.

  1. Start by reducing the image resolution – for batch jobs, I use Adobe Photoshop’s image processor script to downsize images to fit 1920 x 1200 pixels
  2. Alternatively, if you’re working on a static project – where specific images will be used only in specific places – you could use your design software (nearly all mainstream UI software allows you to do this now) to export your images at 2x size to support devices with high pixel densities.
  3. I also convert my image color profiles to SRGB to ensure consistency across most modern display types (this one’s optional)
  4. I then take my newly downsized images and run them through imageOptim at 80% quality. Generally I would aim to get my images under 300kb – if there are any that are still significantly over this target once compressed, I’d run these through again at 70% quality (I wouldn’t recommend going lower than this, though).

Don’t forget you can also do this for PNGs! Enabling PNGCrush in imageOptim will let you significantly reduce the size of PNGs… just be ready for it to take a while.

Make Your Vectors SVG-Easy to Use

If your design contains graphics or illustrations you created using vector software, it can be used on the web as an SVG file. Usually, these files will be a lot smaller than JPGs or PNGs. You can export graphics in most (if not all) vector software in this format.

Optionally, you could use imageOptim or SVGOMG to compress the SVG code without sacrificing quality. Your developer might already use a script that does this automatically when processing the site for production, so it may be worth asking ahead.

Get Your Licenses in Check

If you’re using premium fonts, make sure you’ve purchased a webfont license so you can hand over the correct files to the developer. I’d recommend doing this sooner rather than later – although not often, occasionally web versions of fonts can have slightly different bounding boxes to their desktop counterparts, making it a real pain for developers to work with further down the line.

If you’ve been using samples of stock photos (or if you’ve been going crazy lifting whatever you can find on Google Images), make sure everything is kosher before you go live. Make sure you purchase licensed photos, and if certain photos you want to use require attribution, make the developer aware of this.

Source

p img {display:inline-block; margin-right:10px;}
.alignleft {float:left;}
p.showcase {clear:both;}
body#browserfriendly p, body#podcast p, div#emailbody p{margin:0;}

Source de l’article sur


The daily stand-up is broken. 

No wonder. It was invented almost 30 years ago and we’re still running it the exact same way.

When daily stand-up meetings started in the early 90s, the software development process looked very different. Git didn’t exist. Jira didn’t exist. Collaboration tools didn’t really exist. DevOps didn’t exist. Automation tools didn’t exist. Analytics tools didn’t exist.

Source de l’article sur DZONE


There was a Twitter interaction about testers being invited or not to team meetings and about providing value to the team.

And it got me thinking.

Source de l’article sur DZone (Agile)

We’ve all been there: the kick-off meeting that was nothing more than 60 minutes of your life that you’ll never get back. So now that it’s your turn to run one, you’re determined not to go down the same path.

But where did those kick-off-meetings-gone-wrong actually go wrong? What were their fatal flaws? And how can you make your meeting a good use of everyone’s time?

Source de l’article sur DZone

Meetings are an intrinsic part of professional life. Meetings provide employees the opportunity to share ideas, network, improve their understanding of each other, and update employees and management alike on new developments.

However, when meetings are unplanned, they disrupt the entire work environment. Without a set meeting agenda, it is difficult to know whose attendance is a must for the meeting to be a success. Do you need the large conference room or the small one?

Source de l’article sur DZone

When you think of feedback at work, those yearly assessment and feedback forms flash across your mind. Although these annual performance reviews are helpful, it can also be helpful for managers to look beyond them.

Employees want their work to be recognized. They want to know how they’re doing and if what they do is effective enough.

Source de l’article sur DZone