<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ronald Mendez on Medium]]></title>
        <description><![CDATA[Stories by Ronald Mendez on Medium]]></description>
        <link>https://medium.com/@ramendezb?source=rss-55298c2db329------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*AfV070qI34qPRDnW_rqorw.jpeg</url>
            <title>Stories by Ronald Mendez on Medium</title>
            <link>https://medium.com/@ramendezb?source=rss-55298c2db329------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:28:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ramendezb/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Owning the Role of the Frontend Developer]]></title>
            <link>https://medium.com/@ramendezb/owning-the-role-of-the-frontend-developer-4c5fe8284863?source=rss-55298c2db329------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c5fe8284863</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Ronald Mendez]]></dc:creator>
            <pubDate>Tue, 27 Feb 2018 13:30:00 GMT</pubDate>
            <atom:updated>2019-12-01T02:35:06.727Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Two years ago, I was appointed with the task of leading a small team of developers, which would eventually be the beginning of a completely new phase in my career. A couple of months later, I started writing an article in which I would gather some of my experiences that lead me to that role. I didn’t publish it in my Medium account at the moment because I had the crazy idea of pitching it to one of my long-time favorite online publications, A List Apart.</em></p><p><em>To my surprise, </em><a href="https://alistapart.com/article/owning-the-role-of-the-front-end-developer/"><em>it went on to be published</em></a><em>.</em></p><p><em>Earlier this week, after 22 months, I had the thrill of </em><a href="https://www.smashingmagazine.com/2019/11/future-beyond-writing-great-code/"><em>having a new article featured in a major publication</em></a><em>. It triggered me to revisit my previous article.</em></p><p><em>I was happy to find it still relatable to this day, which lead me to share it once again.</em></p><p><em>*Reprinted with the permission of </em><a href="http://www.alistapart.com/">A List Apart</a><em>.</em></p><p>When I started working as a web developer in 2009, I spent most of my time crafting HTML/CSS layouts from design comps. My work was the final step of a linear process in which designers, clients, and other stakeholders made virtually all of the decisions.</p><p>Whether I was working for an agency or as a freelancer, there was no room for a developer’s input on client work other than when we were called to answer specific technical questions. Most of the time I would be asked to confirm whether it was possible to achieve a simple feature, such as adding a content slider or adapting an image loaded from a CMS.</p><p>In the ensuing years, as frontend development became increasingly challenging, developers’ skills began to evolve, leading to more frustration. Many organizations, including the ones I worked for, followed a traditional waterfall approach that kept us in the dark until the project was ready to be coded. Everything would fall into our laps, often behind schedule, with no room for us to add our two cents. Even though we were often highly esteemed by our teammates, there still wasn’t a chance for us to contribute to projects at the beginning of the process. Every time we shared an idea or flagged a problem, it was already too late.</p><p>Almost a decade later, we’ve come a long way as frontend developers. After years of putting in the hard work required to become better professionals and have a bigger impact on projects, many developers are now able to occupy a more fulfilling version of the role.</p><p>But there’s still work to be done: Unfortunately, some frontend developers with amazing skills are still limited to basic PSD-to-HTML work. Others find themselves in a better position within their team, but are still pushing for a more prominent role where their ideas can be fostered.</p><p>Although I’m proud to believe I’m part of the group that evolved with the role, I continue to fight for our seat at the table. I hope sharing my experience will help others fighting with me.</p><h3>My road to earning a seat at the table</h3><p>My role began to shift the day I watched <a href="https://www.youtube.com/watch?v=o76qx7ZzFs4">an inspiring talk by Seth Godin</a>, which helped me realize I had the power to start making changes to make my work more fulfilling. With his recommendation to demand responsibility whether you work for a boss or a client, Godin gave me the push I needed.</p><p>I wasn’t expecting to make any big leaps-just enough to feel like I was headed in the right direction.</p><h3>Taking small steps within a small team</h3><p>My first chance to test the waters was ideal. I had recently partnered with a small design studio and we were a team of five. Since I’d always been open about my soft spot for great design, it wasn’t hard to sell them on the idea of having me begin to get a bit more involved with the design process and start giving technical feedback before comps were presented to clients.</p><p>The results were surprisingly amazing and had a positive impact on everybody’s work. I started getting design hand-offs that I both approved of from a technical point of view and had a more personal connection with. For their part, the designers happily noticed that the websites we launched were more accurate representations of the comps they had handed off.</p><p>My next step was to get involved with every single project from day one. I started to tag along to initial client meetings, even before any contracts had been signed. I started flagging things that could turn the development phase into a nightmare; at the same time I was able to throw around some ideas about new technologies I’d been experimenting with.</p><p>After a few months, I started feeling that my skills were finally having an impact on my team’s projects. I was satisfied with my role within the team, but I knew it wouldn’t last forever. Eventually it was time for me to embark on a journey that would take me back to the classic role of the frontend developer, closer to the base of the waterfall.</p><h3>Moving to the big stage</h3><p>As my career started to take off, I found myself far away from that five-desk office where it had all started. I was now working with a much bigger team, and the challenges were quite different. At first I was amazed at how they were approaching the process: the whole team had a strong technical background, unlike any team I had ever worked with, which made collaboration very efficient. I had no complaints about the quality of the designs I was assigned to work with. In fact, during my first few months, I was constantly pushed out of my comfort zone, and my skills were challenged to the fullest.</p><p>After I started to feel more comfortable with my responsibilities, though, I soon found my next challenge: to help build a stronger connection between the design and development teams. Though we regularly collaborated to produce high-quality work, these teams didn’t always speak the same language. Luckily, the company was already making an effort to improve the conversation between creatives and developers, so I had all the support I needed.</p><p>As a development team, we had been shifting to modern JavaScript libraries that led us to work on our applications using a strictly component-based approach. But though we had slowly changed our mindset, we hadn’t changed the ways we collaborated with our creative colleagues. We had not properly shared our new vision; making that connection would become my new personal goal.</p><p>I was fascinated by <a href="http://atomicdesign.bradfrost.com/chapter-4/#death-to-the-waterfall">Brad Frost’s “death to the waterfall” concept</a>: the idea that UX, visual design, and development teams should work in parallel, allowing for a higher level of iteration during the project.</p><p>By pushing to progressively move toward a collaborative workflow, everyone on my team began to share more responsibilities and exchange more feedback throughout every project. Developers started to get involved in projects during the design phase, flagging any technical issues we could anticipate. Designers made sure they provided input and guidance after the projects started coming to life during development. Once we got the ball rolling, we quickly began seeing positive results and producing rewarding (and award-winning) work.</p><p>Even though it might sound like it was a smooth transition, it required a great amount of hard work and commitment from everybody on the team. Not only did we all want to produce better work but we also needed to be willing to take a big leap away from our comfort zones and our old processes.</p><h3>How you can push for a seat at the table</h3><p>In my experience, making real progress required a combination of sharpening my skills as a frontend developer and pushing the team to improve our processes.</p><p>What follows are more details about what worked for me-and could also work for you.</p><h3>Making changes as a developer</h3><p>Even though the real change in your role may depend on your organization, sometimes your individual actions can help jump-start the shift:</p><ul><li><strong>Speak up.</strong> In multidisciplinary teams, developers are known as highly analytical, critical, and logical, but not always the most communicative of the pack. I’ve seen many who quietly complain and claim to have better ideas on how things should be handled, but bottle up those thoughts and move on to a different job. After I started voicing my concerns, proposing new ideas, and seeing small changes within my team, I experienced an unexpected boost in my motivation and noticed others begin to see my role differently.</li><li><strong>Always be aware of what the rest of the team is up to.</strong> One of the most common mistakes we tend to make is to focus only on our craft. To connect with our team and improve in our role, we need to understand our organization’s goals, our teammates’ skill sets, our customers, and basically every other aspect of our industry that we used to think wasn’t worth a developer’s time. Once I started having a better understanding of the design process, communication with my team started to improve. The same applied to designers who started learning more about the processes we use as frontend developers.</li><li><strong>Keep core skills sharp.</strong> Today our responsibilities are broader and we’re constantly tasked with leading our teams into undiscovered technologies. As a frontend developer, it’s not uncommon to be required to research technologies like WebGL or VR, and introduce them to the rest of the team. We must stay current with the latest practices in our technical areas of focus. Our credibility is at stake every time our input is needed, so we must always strive to be the best developers in the business.</li></ul><h3>Rethinking practices within the company</h3><p>In order to make the most of your role as a developer, you’ll have to persuade your organization to make key changes. This might be hard to achieve, since it tends to require taking all members of your team out of their comfort zones.</p><p>For me, what worked was long talks with my colleagues, including designers, management, and fellow developers. It’s hard for a manager to turn you down when you propose an idea to improve the quality of your work and only ask for small changes. Once the rest of the team is on board, you have to work hard and start implementing these changes to keep the ball rolling:</p><ul><li><strong>Involve developers in projects from the beginning.</strong> Many companies have high standards when it comes to hiring developers but don’t take full advantage of their talent. We tend to be logical thinkers, so it’s usually a good idea to <a href="https://www.smashingmagazine.com/2014/11/why-you-should-include-your-developer-in-the-design-process/">involve developers in many aspects of the projects</a> we work on. I often had to take the first step to be invited to project kickoffs. But once I started making an effort to provide valuable input, my team started automatically involving me and other developers during the creative phase of new projects.</li><li><strong>Schedule team reviews.</strong> Problems frequently arise when teams present to clients without having looped in everyone working on the project. Once the client signs off on something, it can be risky to introduce new ideas, even if they add value. Developers, designers, and other key players must come together for team reviews before handing off any work. As a developer, sometimes you might need to raise your hand and invest some of your time to help your teammates review their work before they present it.</li><li><strong>Get people to work together.</strong> Whenever possible, get people in the same room. We tend to rely on technology and push to communicate only by chat and email, but there is real value in face time. It’s always a good idea to have different teammates sit together, or at least in close enough proximity for regular in-person conversation, so they can share feedback more easily during projects. If your team works remotely, you have to look for alternatives to achieve the same effect. Occasional video chats and screen sharing can help teams share feedback and interact in real time.</li><li><strong>Make time for education.</strong> Of all the teams I’ve worked on, those that foster a knowledge-sharing culture tend to work most efficiently. Simple and casual presentations among colleagues from different disciplines can be vital to creating a seamless variety of skills across the team. So it’s important to encourage members of the team to teach and learn from each other.</li><li>When we made the decision to use only a component-based architecture, we prepared a simple presentation for the design team that gave them an overview of how we all would benefit from the change to our process. Shortly after, the team began delivering design comps that were aligned with our new approach.</li></ul><p>It’s fair to say that the modern developer can’t simply hide behind a keyboard and expect the rest of the team to handle all of the important decisions that define our workflow. Our role requires us to go beyond code, share our ideas, and fight hard to improve the processes we’re involved in.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c5fe8284863" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Basic rules for happily listening to music in an open office]]></title>
            <link>https://medium.com/@ramendezb/basic-rules-for-happily-listening-to-music-in-an-open-office-a61b45067be3?source=rss-55298c2db329------2</link>
            <guid isPermaLink="false">https://medium.com/p/a61b45067be3</guid>
            <category><![CDATA[entertainment]]></category>
            <category><![CDATA[music]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[workplace]]></category>
            <dc:creator><![CDATA[Ronald Mendez]]></dc:creator>
            <pubDate>Sat, 16 Dec 2017 04:35:23 GMT</pubDate>
            <atom:updated>2017-12-17T01:16:05.411Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gQ-l0W6zqsKgjqiiVMzyaA.jpeg" /></figure><p>Music is a key player in the workdays of those of us who make a living in front of a computer. Though many prefer having full control of what they feed their ears, it can be a good idea to collaborate through shared speakers.</p><p>The only problem is that an office jukebox can produce conflicts when it comes to simple things like choosing a song or setting a proper volume.</p><p>After a couple of years of collaborating and fighting over the music played in an office of more than sixty people, I decided to write down some basic rules to help ease out tension and keep the workplace in harmony.</p><h3>1. Mind the volume</h3><p>Find the sweet spot. Sometimes it’s hard, but it is the only way it’ll work out. In my office it can get tricky, considering that not all desks are at an equal distance from the speakers, so not everyone gets the same dose of decibels. We found that trial and error is the best approach to calibrating the perfect accepted volume range.</p><p>An easy way of knowing if it’s too loud is if you can hear background music while you’re playing something else on your headphones.</p><h3>2. Rules ain’t for fools</h3><p>Whether they’re unwritten, unspoken or <a href="https://www.bloomberg.com/news/articles/2017-05-17/inside-the-offices-where-the-music-never-stops-and-everyone-is-dj">printed out as a giant poster</a>, it’s always nice to set some basic ground rules. Maybe not from the get-go, but maybe after some legal precedent you’ll have to start drafting some clauses.</p><h3>3. Keep the flow going</h3><p>There’s nothing worse than an awkward silence. So if you’re going to get behind the wheel, make sure you’re in it for the long run. It doesn’t have to be hours of music, but make sure to keep it going for a while before stepping down.</p><h3>4. Not so rough</h3><p>Unless you want to bring out your colleague’s killer instinct, I would suggest leaving <a href="https://open.spotify.com/track/3AUZ0xoGYKBpN6LsgZ1QnM"><em>Egg Raid On Mojo</em></a><em> </em>just for your headphones. Although it’s great to use music to pick up the pace around the office, it’s important to not burn the house down.</p><h3>5. Not so blue either</h3><p>Many would agree that softer music is better to keep everyone in a calm state and not interfere with people’s work. But let’s not mistake that for downright depressive music. Keep in mind that sometimes you simply might have a hard time getting through the day, so maybe some mood-killing music might turn out to be the Debbie Downer you definitely don’t need.</p><p>I’m a fan of Radiohead, but let’s be clear you might want to reconsider playing the whole discography <a href="https://open.spotify.com/track/4Na0siMtWOW9pJoWJ1Ponv">without leaving some songs out</a>.</p><h3>6. Careful, careful</h3><p>I personally don’t think that I can be offended by an individual track, but not everyone is the same. Sometimes it might not be the song itself, but the context could stir things ups. Make sure you aim to avoid casualties during your quest.</p><p>You definitely should consider leaving <a href="https://open.spotify.com/artist/58Dx4HPzeOO3dbpD9YYEes">2 Live Crew jams</a> out of the mix, even if you still haven’t gotten over the death of Fresh Kid Ice.</p><h3>7. Mix things up</h3><p>Even if you have great taste in music and love playing the best bands ever, people get tired of repetition. Try not to play a song more than once in a day and try not to play the same band straight for more than a handful of songs.</p><h3>8. (Chinese?) Democracy is the only way</h3><p>I get it, you might not be a big fan of democracy. Trump. Maduro. Brexit. The people’s choice is not always the right choice, but when it comes to blasting speakers, you have to listen to the masses.</p><p>Let your co-workers have the chance to ban a song if needed. If someone gets crazy with power, have a clause that allows removing their DJ benefits for a while without having to get into a big discussion.</p><h3>9. Don’t be sneaky, man</h3><p>If you don’t like a song, say it. If you want to take control, ask. If you think it’s too loud, request to lower the volume. Easy-peasy.</p><p>There’s nothing worse than someone operating from the shadows. Be sure to put a face to any complaints you might have. Your own face, that is.</p><h3>10. Have fun</h3><p>It may sound redundant, but if people are not having fun then maybe your office might not be ready for this emotional roller coaster of a social experiment. After all, we would only do something like this just to have a better working environment.</p><p><em>Although I tend to write about topics completely different than this, I thought it would be nice to share my point of view about a topic I never read about. Then I started doing some research and found some great posts about offices sharing music and </em><a href="https://smashingboxes.com/blog/meet-maestro-turn-spotify-into-a-workspace-jukebox-through-slack-integration/"><em>came upon this cool slack integration</em></a><em> that I just might give a try in my office anytime soon.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a61b45067be3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What makes web design unique among the rest of the design disciplines?]]></title>
            <link>https://medium.com/@ramendezb/what-makes-web-design-unique-among-the-rest-of-the-design-disciplines-671695b69fe4?source=rss-55298c2db329------2</link>
            <guid isPermaLink="false">https://medium.com/p/671695b69fe4</guid>
            <category><![CDATA[abstract]]></category>
            <category><![CDATA[web]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Ronald Mendez]]></dc:creator>
            <pubDate>Mon, 03 Jul 2017 00:18:11 GMT</pubDate>
            <atom:updated>2017-07-03T00:18:11.903Z</atom:updated>
            <content:encoded><![CDATA[<p>Just as many colleagues and people from the creative industry did, I decided to check out <a href="https://www.netflix.com/title/80057883">Abstract: The Art of Design</a>, the new documentary series. I have to say some of the episodes really inspired me, so I took on the whole series in a couple of days.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m9YkmyyX80IOg8wYl7omTw.png" /></figure><p><em>*I originally wrote this post on February 2017, but I was waiting to see one pending episode of the show before publishing. I guess I’m pleading “better late than never”.</em></p><h3>The discipline breakdown</h3><p>During my binge, I noticed that even though all of the disciplines share principles and goals, every process was unique. Trying to picture it in a more logic way, I broke down the disciplines in three different groups.</p><ol><li><strong>Design of physical products or spaces</strong></li></ol><p>These were those disciplines in which the designer has a highly creative vision, takes it to a digital (or paper) format so that it could be built or manufactured. The design is the process right in between the idea and the physical creation.</p><p>Footwear design, architecture, and automotive design were exciting to discover since we are used to seeing the end results in our daily life, but this time we got a peek into the process.</p><p><strong>2. Design as a final product</strong></p><p>In the documentary, graphic design was the only discipline in this category that was explored. What made it stand out is that in many cases the format in which the designer works is the actual product that makes it to the public.</p><p>Graphic design is not a blueprint for a product, it is the product. So, in this case, we see that the final product is often in a digital format.</p><p><strong>3. Design as a form of art</strong></p><p>In my perception, illustration and photography can be defined more as an art process instead of a design process.</p><p>In the case of illustration, I believe there was a phase of design (when the illustrations became magazine covers), but separate from the process we were focusing on.</p><p>The photography episode was even more clear to me. It was pure art. I honestly believe that no actual design process was witnessed.</p><h3>Where do we leave web design?</h3><p>Even though the series didn’t cover the design discipline that I have come to love, I thought it would be a good idea to see in which category it would fall. To my surprise, it didn’t entirely match any of the categories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ttk7I-lYtP42RvRKJBwBGQ.png" /></figure><p>A web designer puts together visual digital products, which are later created (all over again) with a different set of tools.</p><p>From this point of view, it would be similar to graphic design since the final product is digital. But the main difference is that the final product, though digital, is crafted by a non-designer: Cue the lights. Drumroll. Enters the web developer.</p><p>So what’s wrong with that? Nothing. Just that it puts web design into <strong>a unique category in which a design is handed off, but the other party puts together a digital product </strong>as well.</p><p>That is perhaps one of the reasons why web design has the potential to be so magical. It’s a discipline that combines teams of opposing talents, that come together to create digital greatness.</p><p>This has allowed the industry to grow and evolve at such a pace, that every year we see our expectations exceeded in a scary way.</p><p>Although there is still much room for improvement (more on that later), I leave you with a list of my personal favorite projects in which design and development have come together to simply wow the world:</p><ul><li><a href="http://www.because-recollection.com/">Because Recollection</a></li><li><a href="https://throughthedark.withgoogle.com/">Through the Dark</a></li><li><a href="https://www.cartoonnetworkstudios.com/">Cartoon Network Studios</a></li><li><a href="http://falter.madebywild.com/#en">Falter Inferno</a></li><li><a href="https://www.awwwards.com/sites/rainforest-foods-interactive-journey">Rainforest Foods Experience</a></li><li><a href="http://counterclimate.converse.com/">Converse Diamonds</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=671695b69fe4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The fundamental steps for landing a dream job in the creative industry]]></title>
            <link>https://medium.com/@ramendezb/3-basics-to-landing-a-dream-job-25c644c49c7f?source=rss-55298c2db329------2</link>
            <guid isPermaLink="false">https://medium.com/p/25c644c49c7f</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Ronald Mendez]]></dc:creator>
            <pubDate>Sun, 26 Feb 2017 00:48:26 GMT</pubDate>
            <atom:updated>2017-02-28T01:19:51.690Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ch4K_15rJqH32cXHVc_flw.png" /></figure><p>After writing <a href="https://www.linkedin.com/pulse/my-untold-story-landing-dream-job-ronald-m%C3%A9ndez">a retrospective post</a> where I retraced the steps of my personal journey towards the job of my dreams, I created a simple list that anyone can check right before approaching a life-changing career move:</p><h3>1. Find the right fit</h3><p>Not every great company is a perfect fit for everyone. Most of the times it’s simply a combination of the type of work you want to do, the company culture and even in which step of your career you find yourself in.</p><p>One of the first things to look for in a company is quality work. If you find yourself constantly in awe of the projects published by studio, you might want to find out more about the place where the magic sparks.</p><p>Look in places where you often find inspiration. If you’re a designer, you might find amazing studios featured in places like <a href="https://dribbble.com/places">Dribbble</a> of Behance. If you’re looking for a job creating digital experiences, the agency directories of <a href="https://www.awwwards.com/winner-list/">Awwwards</a> and <a href="https://thefwa.com/profiles">The FWA</a> usually showcase the latest and greatest.</p><p>Some companies produce amazing work, but you might notice that a regular day on the job there is the complete opposite of your desired routine.</p><p>Look for a place where you could see yourself fitting in. Are they strictly morning people? Does the team celebrate victories with a cold beer? Are they more tech-oriented or creative? Try to find an answer to questions like these before moving forward. Be sure to snoop around the company’s Facebook page, Instagram and blog posts.</p><p>One last thing to confirm if you’re a match is seeing if the company is actually looking for somebody like you. You might be a seasoned pro, but if they’re trying to find an intern to join the squad, it might not be the right moment to apply. If you take your search seriously, it’s just a matter of time before reading a job description that basically sounds like your profile.</p><h3>2. Do your homework</h3><p>Even the best professional boxers have to go through long preparation before a big fight. The key is to have both short-term and long-term prepping.</p><p><strong>Preparing short-term</strong> is the easiest. You might have found a heaven-made match and all you need is to get ready to make contact. That’s when you need to learn everything you can about the company.</p><p>Find out who the key players are, what they look for in their team and make an effort to learn about their projects. If you love some of their work, it might come in handy to mention it down the road. People who love their work feel flattered upon genuine respect and recognition.</p><p>The trickiest part is the<strong> long-term preparation</strong>. This is the type of homework that you can’t pull off in a couple of weeks. Sometimes you can find a right match without being quite ready for the challenge. The best you can do is invest the necessary time to be the right person for the job.</p><p>Let’s say they need a person with proven experience using a specific programming language and you simply have built your projects with something different. It might be better to take some time to learn a bit and have a couple of projects under your belt before making a move.</p><h3>3. Be ready to take action</h3><p>You’re probably be going solo to the prom if you don’t find the courage to ask the question. A lot of people miss out on great opportunities every day, just because they think they’re not ready. Sometimes they are, but simply might not know it.</p><p>For most of the jobs I’ve had in my career, I wasn’t sure that I had what it took. Only to realize that it’s not as hard as it seems after a couple of weeks on the job. So if you’re having second thoughts on whether you’re worthy or not, take the plunge and find out. The worst thing that can happen is rejection, which is something you can definitely learn from.</p><p>In case you find yourself rejected, there’s no need to cry (or maybe just a little). It’s important to learn from every experience, so if the answer is a cold “no” don’t be afraid to ask why. A few words of feedback might be just what you need to land your dream job on the next try.</p><p>So try to find your match, get ready and make your move. It worked for me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25c644c49c7f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why developers also need design inspiration]]></title>
            <link>https://medium.muz.li/why-developers-also-need-design-inspiration-b67ff15b33b6?source=rss-55298c2db329------2</link>
            <guid isPermaLink="false">https://medium.com/p/b67ff15b33b6</guid>
            <category><![CDATA[inspiration]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Ronald Mendez]]></dc:creator>
            <pubDate>Sun, 19 Feb 2017 18:48:30 GMT</pubDate>
            <atom:updated>2017-02-19T22:02:14.134Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Rnj5o5S_bCC7Bg8tzabRg.png" /></figure><p>I have always been a fan of that thin line between web design and development. It’s always been exciting to cross it any time an opportunity comes and makes us dip our toes in uncharted waters.</p><p>After years of working in the front line of web development, I’ve learned some valuable design lessons that allowed me to find that every day it’s becoming more important for developers to boost our design skills in order to keep up with the industry.</p><h3>The value of inspiration</h3><p>As far as I can remember, designers have always used visual inspiration to ignite their creativity. It simply seems like the natural thing to do. Great designers keep their technique up to date and take in loads of inspiration to create new and exciting work.</p><p>Design inspiration makes up such an important part of the internet, that in every corner we are able to find new projects filled with fresh illustration, branding, user interfaces and interactions, to name a few.</p><p>The only problem is that many developers have seen this habit of surfing through visual inspiration as something totally unrelated to our work. The truth is that design is indirectly an important part of what we do, so keeping those skills fresh has become a must-have.</p><p>In my personal experience, the best way to keep our design chops sharp is by taking daily doses of visual inspiration, just like designers do.</p><h3>The key benefits for developers</h3><p>Great inspiration requires dedication.</p><p>Finding the right sources and working valuable time into your schedule can only be accomplished with great sacrifice. So it’s important to know the rewards that can come from such efforts:</p><p><strong>Enhancing collaboration</strong></p><p>Digital projects require multi-disciplinary teams to work closer every time and a seamless collaboration between all parties is essential.</p><p>Since design professionals are known to be up to date on the latest industry trends, it has become necessary for their tech counterparts to be on the same page. When all members of the team approach a project share common references and examples of work, it is more likely to yield better collaboration. If a developer can anticipate some of the ideas that are coming his way, he will surely have a clear approach on the execution and techniques to use.</p><p><strong>Pushing boundaries</strong></p><p>When developers focus only on technical skills, they’re more likely to keep a closed mindset when new ideas are presented.</p><p>It’s not uncommon to hear a developer replying “that can’t be done” to his creative peers. That’s simply a natural reaction when being caught off guard upon a problem that has not been solved before. The best way to approach this scenario is by having an open mind when it comes to creative input.</p><p>Developers who include design inspiration in their diet are more likely to be one step ahead. Seeing shiny out-of-the-box ideas can be a trigger for investigating the techniques to accomplish such ideas.</p><p><strong>Adding value to the project</strong></p><p>Highly efficient teams take pride in having ideas coming from all of their members, even from the ones we might least expect.</p><p>During the early days of the internet, teams where pretty much black and white regarding the creative types and the tech guys. But in recent years we’ve seen these sides come together closer than ever and it is now completely normal to see designers provide input on some aspects of a project’s development. This is only possible when a team’s creatives have a certain level of tech knowledge.</p><p>Although it’s not as common to see developers provide design input, a well-informed coder can have a more logical approach to many aspects of a design. This can lead to more efficient work, but it is only possible when developers take a true interest in the creative side of the projects they’re involved with.</p><p><strong>Unlocking potential</strong></p><p>As myself, I know of many developers who have creative skills but have put them aside to focus on their logic-based career. But working on multi-disciplinary teams can be an opportunity to dust off some of those skills and putting them to use.</p><p>A constant flow of visual inspiration can trigger a developer into expanding his skill set and becoming more valuable to the team. Having a basic set of design skills can help coders become less dependent when it comes to making important decisions in crucial moments of a project.</p><p>Any developer that has the ability to choose a color for a rollover state, or to adjust a layout for a mobile view, can save the day in any company.</p><p>For me, design inspiration has become an important part of my career and it fuels that special ingredient that gives my work a bit of a boost. On a daily basis, not only do I check out the latest websites, but I also find myself inspired by fresh animations, patterns, interactions and even typography.</p><p>Although there are places where you can get an unlimited dose of inspiration, I’ve always been a fan of those who curate and filter the best content out there. My personal favorites are:</p><ul><li>Going over Muzli Blog’s <a href="https://muz.li/blog/?s=ui+interactions+of+the+week">UI Interactions of the Week</a> is a great way to see beautiful interfaces come to life</li><li>Checking <a href="https://thefwa.com/live-judging/">The FWA’s Live Judging</a> and <a href="http://www.awwwards.com/">Awwward’s Latest Collections</a> to see the best web design out there</li><li>Browsing <a href="https://www.smashingmagazine.com/tag/inspiration/">Smashing Magazine’s inspiration tag feed</a> always caters some great articles</li><li>For many years, <a href="http://www.swiss-miss.com/">Swiss-miss</a> has been a source for all things design, where you can find inspiration in photography, products, links and even quotes.</li><li>The <a href="https://www.behance.net/galleries/8/Interaction">curated Interaction Gallery in Behance</a> always showcases amazing work</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F8153c7%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F8153c7&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/365d4e2e268702353cc960e6b5f12046/href">https://medium.com/media/365d4e2e268702353cc960e6b5f12046/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b67ff15b33b6" width="1" height="1" alt=""><hr><p><a href="https://medium.muz.li/why-developers-also-need-design-inspiration-b67ff15b33b6">Why developers also need design inspiration</a> was originally published in <a href="https://medium.muz.li/">Muzli - Design Inspiration</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>