<?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 Miles Sebesta on Medium]]></title>
        <description><![CDATA[Stories by Miles Sebesta on Medium]]></description>
        <link>https://medium.com/@miles.sebesta?source=rss-692e5f1e6798------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*t_vv1Zp5FHUV1WE3.jpg</url>
            <title>Stories by Miles Sebesta on Medium</title>
            <link>https://medium.com/@miles.sebesta?source=rss-692e5f1e6798------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:24:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@miles.sebesta/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[What failing with 28 start-ups has taught me]]></title>
            <link>https://medium.com/@miles.sebesta/failing-28-start-ups-360198e63350?source=rss-692e5f1e6798------2</link>
            <guid isPermaLink="false">https://medium.com/p/360198e63350</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[edtech]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Miles Sebesta]]></dc:creator>
            <pubDate>Sat, 22 Jun 2019 14:02:06 GMT</pubDate>
            <atom:updated>2019-06-22T15:07:29.845Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-ojleuIV2d1tVEhs" /><figcaption>Photo by <a href="https://unsplash.com/@nate_dumlao?utm_source=medium&amp;utm_medium=referral">Nathan Dumlao</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Yep, 0 and 28; that is my startup record. 100% of the time companies I work with fail. 100– that hurts a bit.</p><p>You might be asking, “Who the heck are you? And why do you suck so much at this entrepreneurship thing?”</p><p>Great questions, let’s start with who the heck I am.</p><p>I’m Miles. As a developer for the past 10 years, I have always worked for startups. But for the past four years, I have been able to watch startups bootstrap from a 100,000-foot ivory tower.</p><p>I work for a private company that specializes in computer programing training. For years, my employer and local school districts have been working together to revolutionize public education.</p><p>For the last four years, I have been assigned to work at a magnet high school where students learn entrepreneurship skills (financing, MVPS, SWOT, LEAN Model, etc.) with the goal of launching a business before they graduate. Not make-believe businesses but real businesses. At least that is the goal.</p><p>During their junior year, students find a problem, create a solution, run M.V.P.s, and pitch their businesses to local investors. Any profits the students make they get to keep.</p><p>Senior year students run their companies.</p><h3>First, a word to the critics</h3><p>Some balking critics might say, “These are high schoolers not running ‘real’ businesses. Why should I care?” Two points.</p><p>One, tell that to the students — a student body that has received over $20,000 in angel investment funding by winning pitch/code competitions, competing against college graduates and entrepreneurs for funding.</p><p>Two, yes, these young entrepreneurs are just that: young, which is why we should pay attention. Soon they will become the workforce, and your clients. ALSO sometimes the wrath of adolescence bursts into the room, filling the space with a tornado of drama and emotion. A drama which leads to extreme conflict; thus allowing the opportunity for extreme conflict resolution.</p><p>For realzies, you should mentor a local entrepreneurship club or company; you will learn a lot.</p><p>Now to the lessons.</p><h3>A wrong hire will kill or save you (no pressure)</h3><p>You might read about the importance of hiring all the time on LinkedIn. Probably to the point where you want to throw up. All those cute little quotes you read like, “hire slow and fire fast” ain’t nonsense. Hiring is damn important.</p><p>For a growing organization, a SINGLE hire can tear down everything. Conversely, the right hire can elevate a team.</p><h3>The wrong subtraction</h3><p>Case in point, one year we had a team primed for success. The group produced a great product concept — to place sensors in your lawn and only water the sectors that need watering. In California, where we have no water, this product naturally attracted lots of attention. The cherry on top? The team was extremely talented.</p><h4>The exciting launch</h4><p>This team of six had it all; prodigy-level technical chops, solid financial insights, and expert level presentation skills.</p><p>Out of the gate, they rolled over the competition in every pitch /code events; winning over $10k in their first year.</p><h4>Success will lead to turbulence</h4><p>If you fly for long enough, you will hit turbulence. The question is, how well is everything bolted down?</p><p>Some laws of physics seemingly apply to business too, “for every action there is an equal and opposite reaction.”</p><p>The <a href="http://innovationfootprints.com/wp-content/uploads/2015/07/startup-genome-report-extra-on-premature-scaling.pdf">Startup Genome Project</a>, a group that studied 3200+ high growth technology startups, boldly stated in their report’s analysis:</p><blockquote>More than 90% of startups fail, due primarily to self-destruction rather than competition. For the less than 10% of startups that do succeed, most encounter several near-death experiences along the way. Simply put, we just are not very good at creating startups yet.</blockquote><p>I guess Diddy was right, “mo money, mo problems.”</p><p>Success, even small amounts, can be intoxicating.</p><p>This team hit some major turbulence because of success. Rather than focusing on their next steps, team members wanted to focus on who should receive the most praise and money.</p><p>The nugget of wisdom: with growth, you can expect conflict.</p><h4>Rough winds are when real leaders emerge</h4><p>Turbulence is when true leadership appears. For this team, a young, powerful woman emerged and was named CEO. She had her team solidify roles; she took care of the front-facing team while her CTO developed the product. But unfortunately, it didn’t last.</p><h4>Losing the captain</h4><p>Sometimes even the best leaders can’t right the ship. After months of fighting her team, the leader threw in the towel.</p><h4>Running out of jet fuel</h4><p>Now that the captain was gone the talent began leaking jet fuel. A once productive team that was continuously coming up with updates turned into a group that missed investor deadlines. Dwindling to just a cool high school project.</p><h4>Moral of the story</h4><ul><li>Early on a single hire or fire can alter your company’s culture.</li><li>You must protect your culture and not let success destroy you.</li><li>Arrogance will kill you like Icarus flying too close to the sun.</li></ul><h3>Now we know it is vital to hire the “right” people, you might be asking how? Or more importantly, who?</h3><h3>First, you need women on your team. Period.</h3><p>I really wish I didn’t have to write this section. I mean it is 2019, but some of us tech-nerd men still don’t get it. You need women on your team.</p><p>Still not listening, dudes? YOU NEED WOMEN ON YOUR TEAM.</p><p>Besides it being 2019 and you know being just the right thing to do, if you HAVE to have numbers know that having women on your team might make your company more successful when it comes to funding, running your company, surviving, all that. As Fishkin puts it,</p><blockquote>Teams with at least one woman founder performed 63 percent better than all male founding teams — <a href="https://twitter.com/randfish?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor">Rand Fishkin</a>, Lost and Founder, Page 157.</blockquote><p>I have seen this truth play out over and over again.</p><p>The four most advanced teams I worked with all had at least one strong female team member.</p><p>Some of these young women took a bold and direct approach. Some took more subtle methods. But in all cases, they were by far the most talented technically and social-emotionally.</p><p>Time and time again, a struggling team that brought in a strong female team member increased production almost instantly.</p><p>Strong teams that lost their vital team member would then crash and burn.</p><p>The all-male teams and male-dominated teams were significantly more likely to underperform when compared to mixed gender teams and all female teams.</p><p>Moral of the story, it is freaking 2019, hire and promote women.</p><h3><strong>When you know, you know.</strong></h3><p>When you find a superstar hire them even if you don’t have a job for them yet. Don’t let the employee of your dreams slip away because you don’t have a job title created.</p><p>From my non-scientific observations, I can tell you this truth:</p><p><strong>You are WAY more likely to hire the WRONG person.</strong></p><p>Regardless of gender, sexual identity, race, sexual preference, background if you find a superstar that fits hire them.</p><p>Design your hiring process to find these super-stars. Since companies are often trying to solve problems quickly, you might be tempted to focus too much on hiring for hard-skills. <strong><em>I promise you, after four years of teaching, it is much easier to teach a hard-skills than foster soft-skills.</em></strong> It is the lack of soft skills that will destroy your team. Hard work and communication will always outpace talent.</p><p>So who do you hire? Per my observations, when given open-ended tasks or projects, individuals fall into five groups: the minimalists, the fabricators, the grinders, thought leaders, and the diamonds. Here are some thoughts about each of these categories.</p><h3>The minimalists</h3><p>Minimalists are just that, minimalists. They do the bare minimum on open-ended tasks; if you are lucky.</p><p>Per my pseudo-scientific observations, 30-33% of the potential workforce is built up of minimalists, making them the most prominent population segment.</p><p>Being a minimalist has nothing to do with a lack of ability but everything to do with motivation. Minimalists need guidance because they lack internal motivation or confidence in a subject.</p><p>However, for whatever freakonomics reason, this group is by far the most creative and often have the best people skills.</p><p>Minimalists are not destined to stay in this group. Once the minimalist has a breakthrough, they morph into unicorns. But this takes a great effort from external sources; it can take years. Others have to believe in minimalists before they believe in themselves.</p><p><strong>How to work with minimalists.</strong></p><ul><li>Invite them to be apart of the design process, but don’t rely on them for significant production.</li><li>Break-up tasks into small chunks, they need to see small wins.</li><li>Try giving them a people-oriented position (e.g., customer support or sales). Often the minimalist’s people skills are superior to other groups. Once you provide the “minimalist” the right task, they often morph into “grinders.” Just don’t expect them to find their kung-fu on their own.</li><li>When a minimalist gets excited leverage the excitement and build their confidence by setting a plan with lots of small wins. This continues to boost their confidence while also helping to hold them accountable.</li><li>Leverage growth mindset practices to teach grit.</li></ul><h3>The fabricators</h3><p><strong>This group scares me the most.</strong></p><p>Even scarier, fabricators come in at a whopping 26-29%.</p><p>Fabricators are extremely talented. However, they are even more talented at disguising themselves as highly effective workers.</p><p>Fabricators spend more time convincing you they did great work rather than doing the job. They settle well below their capabilities and try to convince you they did more.</p><p>Fabricators will get an open-ended project done, but they perform best with milestones.</p><p>Be ready for fabricators to cut corners and give excuses. Don’t allow excuses, stand firm. Anticipate their tendency by baking in extra time for revisions.</p><p><strong>How to work with fabricators.</strong></p><ul><li>Set high standards.</li><li>Don’t pull punches on your critiques.</li><li>Review their work early; set the tone and direction.</li></ul><h3>The grinders</h3><p>You want grinders. Grinders are the workhorses that get stuff done.</p><p>Lucky for society grinders take up 25-28% of the potential workforce.</p><p>Not all grinders start off producing great work; they have various level of ability. However, I promise they outperform every other group over time.</p><p>Grinders are not the most creative; they are not flashy on their solutions. They get it done. Sort of set and forget team players.</p><p>When a grinder is frustrated, it is often too late. Because grinders don’t usually complain, you need to protect this group. A grinder can be easily overworked and taken advantage of by others.</p><p><strong>How to work with grinders.</strong></p><ul><li>You need to protect grinders from burnout. Remind grinders to take breaks.</li><li>Be keenly aware of other group types over using the grinder; you don’t want this person to get burnt out.</li><li>Focus on teaching them new strategies and encourage them to try to reach for higher level skills.</li><li>DON’T micromanage.</li><li>DO encourage and recognize them; they sometimes take a back seat to the “thought leaders.”</li><li>On rare occasions, you will have to motivate them, but if this is happening, you need to take a step back and see if there are more significant issues are in play.</li></ul><h3>The thought leaders</h3><p>Thought leaders have many great ideas and almost naturally take control of a team. But, this group isn’t as uncommon as you think, coming in at about 7-9%.</p><p>Thought leaders are a highly sought-after group. On paper, thought leaders appear great but BEWARE these individuals can be your biggest asset or greatest issue.</p><p>An unhealthy thought leader becomes a dictator and micromanager. They can quickly become the hardest person to work beside. They can single-handedly kill your team’s morale.</p><p>Teams are all about collaboration and balance. You need to teach this lesson to the thought leader. Their arrogance and ego can lead them down a dark path if gone unchecked.</p><h4>Not all thought leaders are hard workers.</h4><p>Being a thought leader does not automatically make them a grinder. Some burn through life purely off talent making them apt to start projects and never finish. Time after time again, I have seen thought leaders bail when situations get hard.</p><p>When a thought leader is frustrated, you need to be ready to spar. A frustrated thought leader will test your leadership. It doesn’t mean that they don’t respect you, but they do want to be heard. Let them have their moment but don’t be afraid to push back with your direction and reasons.</p><p><strong>How to work with thought leaders</strong></p><ul><li>Foster their leadership skills.</li><li>Be aware of their duality, continuously grow them into the leader you for your organization.</li><li>DON’T LET THEM OVERPOWER.</li><li>Encourage them to share ideas and listen.</li><li>Be ready to spar when they are frustrated, overworked, or out of their comfort zone.</li></ul><h3>Diamonds are forever</h3><p>1–2% of the workforce are diamonds — individuals that eventually believe in themselves and turn into rockstars. They are the perfect balance of grinder and thought leader.</p><p>These people are hard to spot and come from all places. Sometimes they are minimalists turned grinder, sometimes they are grinder turned thought leader, etc.</p><p>Often these diamonds are buried in the rough. The team has to believe in them before they believe in themselves.</p><p>Given the perfect conditions, a diamond will emerge and change everything.</p><p>That’s it, well not all of it. But that is enough for one article.</p><p>I hope you consider my failures when you start. But wouldn’t blame you if you don’t… I’m 0–28 remember.</p><h4>One last thing…</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UbUGrbRDabA2WiDqmOOyjg.png" /></figure><h3>TL ; DR</h3><ul><li>Hiring is very important (actually the most important). One team member can make or break your company.</li><li>The highest performing teams ALWAYS have at least one extremely effective female team member.</li><li>The most successful teams are not the smartest or most talented; hard work beats talent every time.</li><li>30–33% of the workforce is minimalists. However, this group tends to be the most creative and friendly. They are wonderful for creative or sales roles if you can motivate them.</li><li>26–29% of the workforce is frustratingly above average minimalists who spend more time and effort settling rather than producing.</li><li>25–28% of the workforce is workhorses/grinders.</li><li>7–9% of the workforce is made up of thought leaders/strategists, but these individuals have a duality of either being a significant asset or hindrance.</li><li>1–2% of the workforce is diamonds in the rough.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=360198e63350" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Re-graduating High School]]></title>
            <link>https://medium.com/@miles.sebesta/re-graduating-high-school-c78a9cba8bde?source=rss-692e5f1e6798------2</link>
            <guid isPermaLink="false">https://medium.com/p/c78a9cba8bde</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[edtech]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[high-school]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Miles Sebesta]]></dc:creator>
            <pubDate>Thu, 06 Jun 2019 16:54:57 GMT</pubDate>
            <atom:updated>2019-06-06T16:57:28.175Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*awYPv_0bNbDRpGtrWPVHYg.jpeg" /><figcaption>First Day of Phillip J. Patiño School of Entrepreneurship High School</figcaption></figure><p>Four years. For four years FUSD and Bitwise Industries have been working in partnership to redefine high school education. For four years we have been quietly building the first public entrepreneurship high school in the United States.</p><p>For four years they took a chance on me, and it has been life-altering. Unfortunately, today is my last day as Mr. Sebesta. I’m graduating high school.</p><p>But I’m so grateful. For four years I’ve seen how compassionate teachers can transform lives. How community members, and private companies, can actively participate in the public school system. How unconditional love and compassion can change our city.</p><p>For four years I’ve seen the grace of God perform miracles before my eyes. From teaching students skills to rise out of poverty, being the first family member to attend college, to telling classmates their sexual preference or identity, to being brave enough to tell an adult they are struggling in life due to homelessness, abuse, or suicidal thoughts.</p><p>I thought I’d go and teach so much, but really all I’ve done is learned.</p><p>Their future is bright because around the world people are wanting to change. For four years we have had VC investors, business leaders, government officials from all sorts of States and countries ask how can they change their community.</p><p>The good news, change is possible. You just need to find superheroes like the Patiño staff that want to change the world. The type of people who treat you like family, and are relentless on their mission.</p><p>The future of our country is bright. Because it is full of love, respect, passion, and solutions. The future is Patiño.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KCSw3jN3MaJfnt7UpFNCIA.jpeg" /><figcaption>First Year; Introduction to Web Development</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3CYMdnz-npSsI26WXudxXA.jpeg" /><figcaption>Mr. Doctor Taylor Halloween</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3h8-8QwBWtRKaTvDBip3WA.jpeg" /><figcaption>Staff Durning the Holidays</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*UbRI4y8FY8xdA0irgQglBg.jpeg" /><figcaption>Mr. Cooksey &amp; His Antics</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OC8sp6PNEeG3cp0eJ2zHLQ.jpeg" /><figcaption>Bloomberg Beta Visit</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e5V0zjwabiGo4xaGn7xOhw.jpeg" /><figcaption>Graduation 2018</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_X4_nc8UA1aWF6rguAuYUQ.jpeg" /><figcaption>Graduation 2018</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6ZPww7wugL8kroCGJmdr7g.jpeg" /><figcaption>Graduation 2019</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c78a9cba8bde" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It’s Time to Fix CSS Animation Keyframes & Timing]]></title>
            <link>https://medium.com/@miles.sebesta/its-time-to-fix-css-animation-keyframes-timing-e393c1d0a756?source=rss-692e5f1e6798------2</link>
            <guid isPermaLink="false">https://medium.com/p/e393c1d0a756</guid>
            <category><![CDATA[scss]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Miles Sebesta]]></dc:creator>
            <pubDate>Thu, 16 May 2019 19:52:34 GMT</pubDate>
            <atom:updated>2019-05-18T16:45:11.750Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rG6FHZR_uh-TDlba" /><figcaption>Photo by <a href="https://unsplash.com/@pankajpatel?utm_source=medium&amp;utm_medium=referral">Pankaj Patel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>First, I love animation. And I love the growing field of CSS animation. But the reality is vanilla CSS animation has, and will always have, major limitations because of how the code is written.</p><p>Animation is not :hover effects. That is movement and movement is not animation, it is movement.</p><p>The word stems from the Latin word <a href="https://www.dictionary.com/browse/animation">animātiō</a> which translates into “bestowing of life”. A powerful definition that has driven years of discovery.</p><p>Today animators employ two different workflow techniques to breathe life into their work: Straight Ahead or Pose to Pose.</p><p>Straight ahead animation is a technique that brings organic life to an animation. You have probably used this technique if you ever made flip-books as a kid while you were bored in class. Straight ahead allows animators to be spontaneous with their drawings, think the flow of conscious writing, or jazz improvisation.</p><p>Let’s say an animator is tasked with drawing a person skateboarding from the left of the frame to the right. Utilizing a straight ahead workflow, the animator first starts drawing the first frame on the left, they know they have to go to the right, but they don’t know how they are going to get there yet. Maybe they have the person jump over a box, or does a crazy flip? The possibilities are endless.</p><p>Through straight ahead the animator discovers how they reach the end while drawing. Not fully planning or thinking head but just allowing the shapes to flow from drawing to drawing.</p><p>Pose to pose focuses on hitting significant poses at specific times. These key poses, or key drawings, in a sequence are what we now call keyframes, key poses, or just keys. In this workflow, an animator first draws and refines the major moments in a scene. They then continue to break down the movement with inbetweens “tweens”. This process gives the animator more control of the final result. It opens up space for animators to push the key moments while keeping a story on track.</p><p>Traditionally senior animators would draw the keyframes, and use a dope sheet, to indicate movement to a more junior animator, called a “tweener”.</p><p>Tweeners fill in the gaps of animation. Today computers do this job. In programs like Maya, animators animate keyframes, while allowing the computer to tween, or fill in the gap.</p><p>For a more visual example, check out this video.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fv8quCbt4C-c%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dv8quCbt4C-c&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fv8quCbt4C-c%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/8cafa20a545fd68243defd193bf86c77/href">https://medium.com/media/8cafa20a545fd68243defd193bf86c77/href</a></iframe><h3>Now the critique…</h3><p>Coding vanilla CSS Animation through a true pose to pose animation technique is incredibly hard. This reality will always limit what can be accomplished through hand-written CSS Animation.</p><h4>One reason, the lack of a universal clock/constant/measurement.</h4><p>The constant for film is 24 frames per second. Every second of animation has twenty-four drawings or 24 frames. Arms, feet, hands, speech, everything happens at 24 frames per second. Life happens at 24 fps; this is the constant. It serves as an internal clock for featured film animators.</p><p>This universal constant allows animators to measure sophisticated movements but more importantly communicate and grow. Life is broken down into single frames, 1/24th of a second at a time.</p><p>Saying that scene needs 3–4 more frames to breath, means the animation is about 0.25 of a second off. Or push this pause and hold it for 12, means stretch the pause out to half a second. Time is paired with the art itself and is embedded in the language.</p><p><strong>For CSS animation time doesn’t exist. There is no universal measurement of time, everything is a percentage.</strong></p><p>For example, let’s say we want to grow an object, using keyframes we would write something like this:</p><pre><a href="http://twitter.com/keyframes">@keyframes</a> animation {<br>0% {<br>    height: 8vw;<br>    width: 8vw;<br>  }<br>50% {<br>    height: 9.5vw;<br>    width: 9.5vw;<br>  }<br>100% {<br>    width: 10vw;<br>    height: 10vw;<br>  }<br>}</pre><p>In traditional film, we know a single keyframe is 1/24 a second. But in CSS what does 50% of keyframes mean? Does it mean 50% of a second? Or 50% of 10 seconds? There is no constant.</p><h3>CSS decouples animation with one of its most important principles: timing.</h3><p>Timing is a key factor in great animation and yet CSS throws it out the window. Timing was so important that early Disney masters extensively write about it and dubbed it as one of the 12 principles of animation.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F93206523%3Fh%3Dd496437eee%26app_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fvimeo.com%2F93206523&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F474456112-5f32b1407abb66c68a8755783c63af82071e0cfd03cd6abfa062fcec6579c969-d_1280&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="760" frameborder="0" scrolling="no"><a href="https://medium.com/media/a5136e7cc9261a75e0fad063493487cf/href">https://medium.com/media/a5136e7cc9261a75e0fad063493487cf/href</a></iframe><p>The 12 principles help animators describe, observe, and master the understandings of the basic laws of physics through drawing. (<em>I included a video that highlights these principles for those interested)</em></p><p>CSS keyframes have no true indication of time, only a fluid percentage point. The perceived effect of the code above is drastically different if it is running on a 1-second animation rate or 10-seconds.</p><p>The fluidity of percentages makes it extremely hard to really fine-tune micro-movements and this is a big problem.</p><p>Seasoned animators can spot issues where timing is off by microseconds, and so can viewers. To viewers, unproperly timed animation feels weightless and lifeless. Viewers might not be able to describe why the animation feels off, they just instinctually know it is off. The animation doesn’t represent the physical world they know. Sure we can write some fancy SCSS mixins and functions like:</p><pre><a href="http://twitter.com/function">@function</a> timing($frames) {<br>  $frame: 0.0416;<br>  <a href="http://twitter.com/return">@return</a> #{($frame * $frames)}s;<br>}</pre><p>And</p><pre><a href="http://twitter.com/function">@function</a> keyframe($frame_num, $animation_length) {<br>  <a href="http://twitter.com/return">@return</a> #{round(($frame_num / $animation_length ) * 100%)};<br>}</pre><p>To produce wackiness like this as an attempt to create somewhat of a constant and help our timing issues:</p><pre><a href="http://twitter.com/function">@function</a> timing($frames) {<br>  $frame: 0.0416;<br>  <a href="http://twitter.com/return">@return</a> #{($frame * $frames)}s;<br>}</pre><pre><a href="http://twitter.com/function">@function</a> keyframe($frame_num, $animation_length) {<br>  <a href="http://twitter.com/return">@return</a> #{round(($frame_num / $animation_length ) * 100%)};<br>}</pre><pre>.animation {<br>  transform-origin: top center;<br>  animation: animation timing(48) infinite;<br>}</pre><pre><a href="http://twitter.com/keyframes">@keyframes</a> animation {<br>  0% {<br>    height: 8vw;<br>    width: 8vw;<br>  }<br>  #{keyframe(24,48)} {<br>    height: 9.5vw;<br>    width: 9.5vw;<br>  }<br>  #{keyframe(48,48)} {<br>    width: 10vw;<br>    height: 10vw;<br>  }<br>}</pre><p>But this still has its limitations, the ones that are inherent with CSS animation. The code becomes exponentially complex when you add multiple objects interacting with each other. The majority of this complexity, troubleshooting the chaining together of sequence timings and delays across multiple objects.</p><p>You start to experience these problems with simple tests like a classic bouncing ball test.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodepen.io%2Fmilessebesta%2Fembed%2Fpreview%2FpmeeaK%3Fheight%3D600%26slug-hash%3DpmeeaK%26default-tabs%3Dcss%2Cresult%26host%3Dhttps%3A%2F%2Fcodepen.io&amp;url=https%3A%2F%2Fcodepen.io%2Fmilessebesta%2Fpen%2FpmeeaK&amp;image=https%3A%2F%2Fscreenshot.codepen.io%2F483823.pmeeaK.small.42ae6cba-d32f-45e5-ac1c-0f5acaed60b8.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codepen" width="800" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/b2e17e31133f78fd170025fd50b6a25c/href">https://medium.com/media/b2e17e31133f78fd170025fd50b6a25c/href</a></iframe><p>Which becomes increasingly frustrating as you try to get slightly more complex movements, that are laughably simplistic to animators.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodepen.io%2Fmilessebesta%2Fembed%2Fpreview%2FvWKbma%3Fheight%3D600%26slug-hash%3DvWKbma%26default-tabs%3Dcss%2Cresult%26host%3Dhttps%3A%2F%2Fcodepen.io&amp;url=https%3A%2F%2Fcodepen.io%2Fmilessebesta%2Fpen%2FvWKbma&amp;image=https%3A%2F%2Fscreenshot.codepen.io%2F483823.vWKbma.small.02805a04-9706-48eb-a4eb-7ade741976a6.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codepen" width="800" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/151b9872bce2edc82679a2bb5c1ea277/href">https://medium.com/media/151b9872bce2edc82679a2bb5c1ea277/href</a></iframe><p>You have to go through great lengths to not only chain together animations, but more importantly, figure out a way to sync them. Case and point:</p><pre><a href="http://twitter.com/function">@function</a> timing($frames) {<br>  $frame: 0.0416;<br>  <a href="http://twitter.com/return">@return</a> #{($frame * $frames)}s;<br>}</pre><pre><a href="http://twitter.com/function">@function</a> keyframe($frame_num, $animation_length) {<br>  <a href="http://twitter.com/return">@return</a> #{round(($frame_num / $animation_length ) * 100%)};<br>}</pre><pre>.ball {<br>  animation: <br>    bounce-one timing(7), <br>    bounce-two timing(10),<br>    bounce-three timing(8), <br>    bounce-four timing(6), <br>    bounce-five timing(4), <br>    roll timing((7+10+8+6+4+2+26)); <br>  animation-delay: <br>    0s, <br>    timing(7), <br>    timing((7+10)), <br>    timing((7+10+8)), <br>    timing((7+10+8+6)), <br>    0s; <br>}</pre><p>The battle against timing forces us to figure out an animation through a straight ahead methodology. Because we don’t have the ability to easily freeze and sequence through keyframes we naturally work on feature by feature. Slowly adding more and more, rather than truly pausing on key moments. Meaning, if we were to animate a bouncing ball first we might animate the left and right movement, then work on the height, then work on the squash and stretch. Rather than focusing on the extreme keys.</p><p>For native, hand-written, CSS animation to fully mature we need to recouple animation to timing. I believe this can be done by:</p><ol><li>Deciding on universal time unit, example 10th of a second or milliseconds.</li><li>Baking the universal time unit into “keyframing”.</li></ol><p>This would allow us to move from code like:</p><pre><a href="http://twitter.com/keyframes">@keyframes</a> animation {<br>0% {<br>    height: 8vw;<br>    width: 8vw;<br>  }<br>50% {<br>    height: 9.5vw;<br>    width: 9.5vw;<br>  }<br>100% {<br>    width: 10vw;<br>    height: 10vw;<br>  }<br>}</pre><p>To something like:</p><pre><a href="http://twitter.com/keyframes">@keyframes</a> animation {<br>0ms {<br>    height: 8vw;<br>    width: 8vw;<br>  }<br>500ms {<br>    height: 9.5vw;<br>    width: 9.5vw;<br>  }<br>1000ms {<br>    width: 10vw;<br>    height: 10vw;<br>  }<br>}</pre><p>Or even:</p><pre><a href="http://twitter.com/keyframes">@keyframes</a> animation {<br>0s {<br>    height: 8vw;<br>    width: 8vw;<br>  }<br>0.5s {<br>    height: 9.5vw;<br>    width: 9.5vw;<br>  }<br>1s {<br>    width: 10vw;<br>    height: 10vw;<br>  }<br>}</pre><p>I believe this would make it drastically easier for designers to create interaction between objects.</p><p>To really take it to the next level we can then.</p><ol><li>Develop the ability to “scrub” or flip back and forth between keyframes which would allow us to utilize a Pose to Pose workflow.</li><li>Develop JS libraries for joints and changing (both IK &amp; FK).</li></ol><p>But both of these points are nearly pointless till we decide to recouple timing to animation.</p><p>Till then programs like hype3 might be our only hope for more complex, story-telling, animations. But that discussion is another post.</p><p>Moral of the story, I love animation. I want to see animation mature more through HTML, CSS, and JS. But before that can happen, I really believe there are some changes that are needed, specifically with timing.</p><p>If nothing changes CSS animation will always struggle to move far beyond just being arbitrary movement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fYiVU1pEDfbumiyk8b1x1w.png" /></figure><p>If you read this post please clap it motivates me to keep writing. Also, I would love to hear your thoughts and feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e393c1d0a756" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 Steps That Can Help You Resolve Stinky Teenage Drama When Your Team Is Acting Like High…]]></title>
            <link>https://medium.com/@miles.sebesta/7-steps-that-can-help-you-resolve-stinky-teenage-drama-when-your-team-is-acting-like-high-ead2c3cdcc0d?source=rss-692e5f1e6798------2</link>
            <guid isPermaLink="false">https://medium.com/p/ead2c3cdcc0d</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <dc:creator><![CDATA[Miles Sebesta]]></dc:creator>
            <pubDate>Sat, 27 Apr 2019 02:31:39 GMT</pubDate>
            <atom:updated>2019-05-18T16:47:00.646Z</atom:updated>
            <content:encoded><![CDATA[<h3>7 Steps That Can Help You Resolve Stinky Teenage Drama When The Team Is Acting Like A Group Of Silly Young High Schoolers!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gGw98Duv_94-goSYzAZC7A.jpeg" /><figcaption>Photo Source: Purchased from <a href="https://www.stockunlimited.com/image/businessman-on-target-with-arrow-next-to-him_1864678.html">StockUnlimited</a></figcaption></figure><p>There was a heaviness to the air as the team members reluctantly plopped down for their weekly. The kind of heaviness that percolates from missed deadlines; radiating out through slumped shoulders, closed arms, and distant gazes. A heaviness that takes over a room as the obviously defeated team stares quietly into the abyss of failure.</p><p>“Good morning”, I half-state, half-ask, as my partner and I greet the reluctant team joining the table. Receiving in return some of those fake half-smiles.</p><p>“What the **** happened?” I thought to myself.</p><p>The once energetic all-star team was silent. They hadn’t produced anything in weeks.</p><p>Whatever the problem, the results weren’t good. It needed intervention yesterday.</p><h3>Does this meeting scenario feel familiar to you?</h3><p>For me, these meetings come with the territory. For the past three years, I have mentored high school entrepreneurs in launching businesses; yep, high schoolers. And spoiler, teenagers sometimes don’t handle conflict or change well… And with my job, we can’t fire anyone.</p><p>Because of this I have seen extreme business conflict and have been forced to practice extreme conflict management.</p><p>Through painful meetings, angry stares, and palpable discontent, I have discovered a solution that can help right the leaning team ship. I wish I could say these were intentionally discovered methods. Really, it was out of desperation at grasping for straws with one of my senior teams. This team was once so fun to watch, and now they were failing, I was failing them.</p><p>Out of desperation, I threw a Hail Mary. The team was falling apart, the meetings were falling apart. What did I have to lose? I had a hunch; why not wing it?</p><p>“I want to try something,” I said as I looked around the table. “I think you are all way too nice to tell me what is happening. So here is what we are going to do; we are going to go around the room and I want each one of you to answer these three questions.”</p><p>“The three questions are,” as I made a number one with my right-hand index finger, “What does success for this team look like to you?”</p><p>After a dramatic pause, I slowly raised a second finger on my hand, “Where are you failing? Meaning, what is stopping you from reaching success? I only want facts, no gossip or name-calling.”</p><p>“Finally, three,” as I changed my fingers again, “how can YOU personally improve to get this project back on track?”</p><p>I then turned and beheld the most aggravated looking teenager, “Looks like you have something to say, why don’t you start?” I stated with a smile.</p><h3>The meeting blew me away.</h3><p>Over the next hour, we were able to unravel all sorts of issues. The meeting revealed that one team member was, in fact, bored, and felt underutilized. They were frustrated in their ability to communicate with the team. The leadership recognized they were micromanaging and not allowing everyone’s voice to be heard. In the end, they all agreed they wanted to get back to making video games and having fun while doing it.</p><p>This team started to bond, and get back to basics, and with that word got out.</p><p>I did not know what I did at the time but other teams began to reach out for help.</p><p>Teenagers are not dumb, they know when they need help. They will reach out only if they feel the person has the tools to help. I believe is the same for employees as well.</p><p>Through more meetings, I have experimented with a system that works pretty well. It won’t solve all of your problems but it can help the team to get back on the right path.</p><h3>A Step by Step Starting Point</h3><p><strong>Step 1: Set Ground Rules.</strong> Let them know everyone will have their turn to speak. State these rules with weight and a solid sturdy tone. Tell the team that you only want facts, not opinions; no bullying will be allowed.</p><p><strong>Step 2: Provide the Questions and Thier Purpose.</strong> Provide the three questions and give a reason why you are asking these questions.</p><p><em>Question 1:</em> What does success for this team look like to you?</p><p><em>The Reason: </em>Conflict can arise when individuals have different motives. What is important to one team member can be meaningless to another. This first question helps the team finds common ground.</p><p><em>Question 2: </em>Why are you failing?</p><p><em>The Reason:</em> This question is intended to cut to the core of the conflict but while still framing the discussion on the team’s collective success. Steer the conversation towards team success; not the individual.</p><p><em>Question 3:</em> How can you improve to get this project back on track?</p><p><em>The Reason:</em> The third question bakes into it a bit of personal fault. Members can always improve and this is the chance for individuals to take ownership in the team’s performance without being singled out or taking all responsibility. The improvement should be actionable, observable, and measurable.</p><p><strong>Step 3: Actively Listen and Reflect. </strong>While the team is answering the questions, make and maintain warm eye contact. Verbally mirror what they share. You should use phrases like, “It seems like that…” or “Do you feel like that…?”</p><p>Summarize their thoughts back to them. Don’t add your own commentary.</p><p>At this stage, you should be focusing on acknowledgment. Let them know they have been heard but don’t solve their problems. Remember acknowledgment isn’t agreement, there is a huge difference.</p><p>If your mirror is wrong, it is okay, they will correct you and probably be grateful you are trying to listen.</p><p><strong>Step 4: Highlight Answers. </strong>Write keywords on a whiteboard or a piece of paper, so you can point out potential conflict or agreements in ideology later.</p><p><strong>Step 5: Summarize. </strong>Point out the conflict you noted earlier; summarize the situation. For example, sometimes the conflict comes down to the goal. Multiple team members might be looking at the project with completely different intentions, one might be extremely passionate while the other is dreading their role.</p><p>You will probably notice of these common causes of group conflict start to emerge: uneven expectations, mismatched goals, miscommunication, lack of support, and burn-out.</p><p><strong>Step 6: Give Next Steps.</strong> At this point, after you have pointed out the conflicts, or communication breakdowns (which there will always be), you can provide the next steps. These next steps are where you make your big bucks, I can’t give you answers for the next steps. The goal of all of this is just to get everyone in a state that is semi-receptive of the next steps.</p><p><strong>Step 7: Send off with Positivity. </strong>After the next steps, transition and focus back on the agreements. There will probably be agreements that came out in the discussion, and if there isn’t I am sure there is a positivity you can hang your hat on.</p><h3>Final Thoughts</h3><p>I am not an expert in conflict management, I have just been kicked in the teeth a few times.</p><p>Yet by doing what I outlined above, I have seen numerous tears shed before hearing, “I am sorry”. I have heard teenagers admit wrongdoing. I have seen students hug and smile.</p><p>If teenagers can do all that, so can your team.</p><p>Don’t expect complete and eternal conflict resolution. Be more focused on identifying the behavior within each teammate that causes the conflict. The more they can see it for themselves the more they will do the work to solve the conflict on their own. Seeing your students work collaboratively is the most rewarding feeling. It should be the same for you and your employees.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fYiVU1pEDfbumiyk8b1x1w.png" /></figure><p>If you read this post please clap it motivates me to keep writing. Also, I would love to hear your thoughts and feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ead2c3cdcc0d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What 73 Technologists Wish They Had Learned in High School]]></title>
            <link>https://medium.com/@miles.sebesta/what-73-technologists-wish-they-had-learned-in-high-school-1352ef40626b?source=rss-692e5f1e6798------2</link>
            <guid isPermaLink="false">https://medium.com/p/1352ef40626b</guid>
            <category><![CDATA[edutech]]></category>
            <category><![CDATA[entrepreneur]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[education-technology]]></category>
            <dc:creator><![CDATA[Miles Sebesta]]></dc:creator>
            <pubDate>Fri, 28 Apr 2017 22:54:10 GMT</pubDate>
            <atom:updated>2019-05-18T16:47:58.557Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Backstory</h3><p>I work for Bitwise Industries and <a href="http://geekwiseacademy.com/">Geekwise Academy</a>, a technology education company in Fresno, California. For the past two years, we have partnered with <a href="http://patinoeschool.org/">Patino School of Entrepreneurship</a> by providing custom courses and curriculum. The “E. School” is a completely free public “pathway” school through Fresno Unified School District. Patino is a different type of school, one I haven’t seen before.</p><p>High Schoolers begin to learn technology development skills (Javascript, PHP, SEO, SEM) and form business plans with other students. All of the classes are taught with a business and entrepreneurship lens. For example, in History, while learning about WWII, students might ask the question, “Yes he was evil but what leadership traits did Hitler utilize to come into power? How can we learn?” In Math, students are asked to find the ROI for a company. All classes are in preparation for their senior year.</p><p>Essentially the program breaks down like so:</p><ul><li>Year One: Learn Entrepreneurship Traits</li><li>Year Two: Start Business Plans, MVP, and Pitch to Investors (real life Sharktank)</li><li>Year Three: Bootstrap it till you make it or die trying</li></ul><p>Senior year is an incubator for their company. We ain’t talking about no fake companies either, like the high school projects we remember. They launch real freaking companies and make real freaking money, well at least that is the goal. Oh yeah, and they get to keep the profits. Imagine making money to pay for their college tuition while in high school. Freaking crazy.</p><p>This year, I have been co-leading the advanced online marketing and web development classes where Juniors begin to execute their plans. At the school the staff pushes experimentation, being okay with failure, ideation, pivoting, and pitching constantly. But I wanted to know are we missing something? What are some lessons that other technologies and entrepreneurs wish they would have learned in high school? So that gave me an idea, fire-up the old Twitter machine and ask new followers a few questions.</p><h3>What did I ask?</h3><p>Through DM on Twitter, I sent hundreds of technologists and developers this message:</p><p>“Random question, I work with 70+ high school entrepreneurs. Do you have any life lessons / business advice / things you wish you would have learned in high school? I am always trying to get better and pass on inspiration.”</p><p>What happened next was remarkable.</p><p>My DM campaign got roughly <strong>a 16.67 engagement rate</strong> and participants delivered crazy insights. Most importantly it gave way to a lot of wonderful discussions. During our talks, I started to notice a few trends. Responses could be clumped into six different categories:</p><ul><li><strong>Younger:</strong> The wish that they would have started learning at a younger age</li><li><strong>Network:</strong> The wish they would have learned to come better networkers or have built a better network</li><li><strong>Movement:</strong> The wish they would have learned how to persevere and to continue moving forward</li><li><strong>Finances:</strong> The wish they would have learned the importance of personal finances</li><li><strong>Fear/Failure:</strong> Learn to overcome the fear of failure. Embracing failure as a learning opportunity.</li><li><strong>Other:</strong> Other meaningful responses</li></ul><h3>So what were the results?</h3><ul><li><strong>10.6%</strong> of the respondents wish high school taught them more about personal finances.</li><li><strong>12.76%</strong> wish they had better networks or started creating one sooner in life.</li><li><strong>12.76%</strong> would have liked to learn how to stay motivated and continue pushing through hard times.</li><li><strong>17%</strong> admit that they wish they would have started sooner in life be it programming, or business development.</li><li><strong>23.4%</strong> wish they would have been able to fail more, to overcome the fear of failure, and to learn that “failure” isn’t bad.</li><li><strong>23.4%</strong> of the responses don’t fall into a direct category.</li></ul><p>Out of the 73 respondents:</p><ul><li><strong>53%</strong> were identified as “Developers”</li><li><strong>25%</strong> were identified as “Technologists”</li><li><strong>19%</strong> were identified as “Front-end Developers”</li><li><strong>1%</strong> were identified as “Back-end Developers”</li><li><strong>1%</strong> were identified as “Other”</li></ul><h3>Some of the notable DMS.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/0*cZteiOk1UCJfxpik.jpg" /></figure><h3>Like this not so scientific study? Please share this infographic 🙂</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*wPoozZy-rUA53OdG.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fYiVU1pEDfbumiyk8b1x1w.png" /></figure><p>If you read this post please clap it motivates me to keep writing. Also, I would love to hear your thoughts and feedback.</p><p><em>Originally published at </em><a href="https://www.milessebesta.com/teaching-technology/technologist-high-school/"><em>https://www.milessebesta.com</em></a><em> on April 28, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1352ef40626b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 Tips to “Pass” the Classic Entry Level Front-end Developer Code Challenge]]></title>
            <link>https://medium.com/@miles.sebesta/tips-front-end-developer-code-challenge-8fec60fe2a47?source=rss-692e5f1e6798------2</link>
            <guid isPermaLink="false">https://medium.com/p/8fec60fe2a47</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Miles Sebesta]]></dc:creator>
            <pubDate>Sun, 19 Mar 2017 02:43:29 GMT</pubDate>
            <atom:updated>2019-05-18T16:48:38.995Z</atom:updated>
            <content:encoded><![CDATA[<h3>7 Tips to “Pass” the Classic Entry Level Front End Developer Code Challenge</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5l4GgHccu7exOm4Q" /><figcaption>Photo by <a href="https://unsplash.com/@tma?utm_source=medium&amp;utm_medium=referral">Tianyi Ma</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Lots of website development shops that focus on CMS development: WordPress, Drupal, Joomla, Magento, etc… offer a “classic” test for front end developers. Even SASS companies will sometimes provide this test.</p><p>What is the test? Take a graphic file and “htmlize” it.</p><p>Whether or not code test provides a decent understanding of the candidate’s abilities is up to debate. Personally, I believe hard-skills can be trained and perfected, soft skills and problem-solving abilities are harder to obtain. But, what do I know? Good or bad, a vast majority of development shops give this test with various degrees of difference. So because of that, here are some tips to help you break through the first round and get that in-person interview.</p><h3>Tip 1: Find your workflow and then practice, practice, practice</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FkAuSfqO0KoeBpHm5HX%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FkAuSfqO0KoeBpHm5HX%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FkAuSfqO0KoeBpHm5HX%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="245" frameborder="0" scrolling="no"><a href="https://medium.com/media/48c3a00aa83ffd3fcd2bb500bbab32e4/href">https://medium.com/media/48c3a00aa83ffd3fcd2bb500bbab32e4/href</a></iframe><p>As a junior developer, you might not be as fast as others, so you need to practice. Just like sports, you can’t show up to a game day without practicing. You need to drill, and re-drill. Practicing is not playing a pick-up game of basketball, practicing is focusing down and becoming better at one particular aspect.</p><p>Development is no different, you need practice. So practice!</p><p>Most companies give two test versions for front end junior developer positions:</p><p><strong>Number 1:</strong> Take this PSD / Sketch/graphic file and htmlize it within an hour</p><p><strong>Number 2:</strong> Take these PSD / Sketch files / graphic files and htmlize it as fast as you can</p><h4>How do you practice?</h4><p>Go to a site like this: <a href="http://freebiesbug.com/psd-freebies/website-template/">http://freebiesbug.com/psd-freebies/website-template/</a> and download a PSD.</p><p>Set a timer for an hour and htmlize as quickly as you can.</p><p>The next day practice again, then the next day practice again, repeat over and over using different graphic files.</p><p><strong>But here is the secret.</strong> When your time is up, reflect and go over your code. What did you spend too much time on? Are there patterns that you can use? Can you recycle coding techniques/frameworks from project to project?</p><p>AGAIN HERE IS THE SECRET, THINK ABOUT YOUR CODE!</p><p>Find and read resources. Research how to write clean code fast. Discover! Because if you keep practicing the wrong techniques you are going to form bad habits.</p><p><strong>Again, step one HTMLize. Step two think!</strong></p><p>Look for ways to speed up your workflow. Create a naming convention. Use tools like <a href="https://avocode.com/">Avocode</a>. Find an IDE you like. Read a lot. It is all practice.</p><h3>Tip 2: Look at the Freaking Job Description</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fl0Iy59GA3gtCEgBkk%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fwow-interesting-thinking-l0Iy59GA3gtCEgBkk&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fl0Iy59GA3gtCEgBkk%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/7ae0944f2053374ab66f95e05f231d9d/href">https://medium.com/media/7ae0944f2053374ab66f95e05f231d9d/href</a></iframe><p>I feel like this is a no-brainer but look at the freaking job description. Then apply the skills they are looking for into your code tests, unless they tell you not to! What do I mean? If the description says “Has knowledge in LESS and SASS”. Guess what, you better write some LESS or SASS.</p><p>If the front end development description has “GitHub”, then maybe you should… just maybe… you should make some commits. Maybe… just maybe… you should give them the GitHub repo.</p><p>If the description has the word “bootstrap,” then maybe you should use bootstrap….</p><p>Get the idea?</p><h3>Tip 3: Ask Clarifying Questions</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fl0HlUG5M4pNZ0X42I%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fpeopleofearthtbs-l0HlUG5M4pNZ0X42I&amp;image=https%3A%2F%2Fmedia2.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExMjN0MW52d2gzeGxrczF3YXp5Nnp1N3J3OTN5bnBhenV1YTRza2U4NyZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2Fl0HlUG5M4pNZ0X42I%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="246" frameborder="0" scrolling="no"><a href="https://medium.com/media/095b2fcbadd311a1870a32d486724851/href">https://medium.com/media/095b2fcbadd311a1870a32d486724851/href</a></iframe><p>If you need to ask questions, then do it! For example, if you are afraid of just jumping into SASS or SCSS for the test. Ask them, “Can I use SCSS on this code test? I ask because SCSS is in my regular workflow, but I want to make sure it is okay.” They will probably be impressed if you ask.</p><h3>Tip 4: Write Clean Code</h3><p>Clean code is pretty evident and where the practice and reflection comes out. Write clean code. Use comments correctly. But, I encourage you to take this a step further! If it is a WordPress development shop, then look at the WordPress Codex. Follow WordPress’s recommendations, same with other systems. If you want to take it to an extreme, read some of the HTML/CSS where you are applying, try to model their naming convention.</p><h3>Tip 5: Have a Naming Convention</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FP5wPrhzZDdeJW%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2FP5wPrhzZDdeJW&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FP5wPrhzZDdeJW%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="278" frameborder="0" scrolling="no"><a href="https://medium.com/media/1c3afd87dd70ffae90c72f6bbffb3e59/href">https://medium.com/media/1c3afd87dd70ffae90c72f6bbffb3e59/href</a></iframe><p>Having a naming convention affirms the point “Write Clean Code.” Writing re-usable CSS is harder than it seems. CSS becomes bloated quickly. There are tons of articles about different methodologies for naming. I prefer BEM (Block Element Modifier) or <a href="https://smacss.com/">SMACSS</a>.</p><p>Don’t just use a naming convention for CSS do it for image assets as well. Example, if you have multiple SVG icons don’t name them twitter.svg and facebook.svg (unless you decide to have a subfolder called icons) make it something like icon-twitter.svg and icon-facebook.svg.</p><h3>Tip 6: Turn the Test in on Time, or Early.</h3><p>Tip 6 is a no brainer, don’t miss your deadline! If you do, turn it in and apologize. You probably won’t get the job, but you should try to save your good name. Your name is your brand.</p><h3>Tip 7: Don’t Stress</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fn60s5QpOQymac%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fn60s5QpOQymac%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fn60s5QpOQymac%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="326" frameborder="0" scrolling="no"><a href="https://medium.com/media/ad8b47837f356c3c36a15c78f6b26e1b/href">https://medium.com/media/ad8b47837f356c3c36a15c78f6b26e1b/href</a></iframe><p>If you don’t get the second interview don’t stress, it wasn’t the job for you. You will get the next one!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fYiVU1pEDfbumiyk8b1x1w.png" /></figure><p>If you read this post please clap it motivates me to keep writing. Also, I would love to hear your thoughts and feedback.</p><p><em>Originally published at </em><a href="https://www.milessebesta.com/web-design/tips-front-end-developer-code-challenge/"><em>https://www.milessebesta.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8fec60fe2a47" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>