<?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 Phil Thompson on Medium]]></title>
        <description><![CDATA[Stories by Phil Thompson on Medium]]></description>
        <link>https://medium.com/@imgiseverything?source=rss-40c32f576127------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*bx1jdUNimEI3zUxE.jpg</url>
            <title>Stories by Phil Thompson on Medium</title>
            <link>https://medium.com/@imgiseverything?source=rss-40c32f576127------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 00:08:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@imgiseverything/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[How to get that first web development job at a web/digital agency]]></title>
            <link>https://medium.com/@imgiseverything/how-to-get-that-first-web-development-job-at-a-web-digital-agency-289d075fac86?source=rss-40c32f576127------2</link>
            <guid isPermaLink="false">https://medium.com/p/289d075fac86</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[Phil Thompson]]></dc:creator>
            <pubDate>Thu, 07 Sep 2017 15:56:14 GMT</pubDate>
            <atom:updated>2017-09-07T15:56:14.170Z</atom:updated>
            <content:encoded><![CDATA[<p>You’ve just graduated from university, or college and you want to get a job as a web developer/web designer, but it turns out it’s much harder than you realised. So how do you get that first job as a web developer?</p><p>Your parents and friends might be telling you that your lack of employment is down to the current economy but here’s the real truth; the truth that your lecturers and parents don’t know: for the vast majority of IT-related courses, everything you are taught is not very useful in a commercial environment and regardless of the economy, that first job can be very difficult to obtain.</p><p>Web agencies seem to want, junior developers to come in and to be able to start work immediately and most graduates can’t do that. Of course, a junior developer will learn on the job and constantly improve and with the help of a good middleweight or senior developers above them, they’ll improve significantly more, but they need to have the basics down first.</p><h3>The basics</h3><p>Every agency is different but the basic tasks for a junior web developer could consist of:</p><ul><li>buying domain names and updating/setting-up DNS on those domains</li><li>setting up a local web server with <a href="https://www.apachefriends.org/">XAMPP</a> or <a href="https://www.mamp.info/en/">MAMP</a> or a more senior dev may have set-up <a href="http://gruntjs.com/">Grunt</a>/<a href="http://gulpjs.com/">Gulp</a> tasks to do this</li><li>building HTML/CSS templates from a Photoshop/Illustrator/Sketch design</li><li>backing up files in version control (probably GIT) and creating Pull Requests and mergin code. Check out <a href="http://www.ohshitgit.com/">ohshitgit</a> for when you make a mistake — and you will ;)</li><li>installing/setting up a new website with the agency’s in-house CMS or open source varieties like WordPress/Drupal/ExpressionEngine etc</li><li>keeping track of time and learning how long it takes to do key tasks</li><li>quickly explaining your previous day’s work and current day’s plans at the morning stand-up meeting</li></ul><p>When I went to university to study Computer Science, I certainly didn’t learn any of those basic skills in lectures or in projects. Some, I picked up in a placement year, where I worked as web designer for the local council, but for the most part I picked those skills up on my own in my spare time and so did everyone else in this field — we’re all self-taught by <a href="http://www.alistapart.com/">blogs</a>, <a href="http://imgiseverything.co.uk/articles/dom-scripting-by-jeremy-keith/">books</a> and <a href="https://boagworld.com/show">podcasts</a>.</p><h3>How I got my first job…</h3><p>In my first year at uni (2001–02), the lecturer in charge of industrial placements told us that there were ‘<em>no jobs in web design/development</em>’, this made my heart sink. However, a year later when the work placements started to be advertised on the university notice boards, at least half were for web based jobs. I decided then and there that I wanted to be a web developer and that such a thing was actually possible. Sadly, every placement I applied for wanted me to have experience which I didn’t have.</p><p>After six months of trying to get a placement which involved lots of (failed) interviews, I realised I needed some hands-on experience to get any sort of credibility with interviewers, so I started to maintain the website (for free) of the charity that my then girlfriend’s mother worked for. My CV now had some experience and a URL on it. In interviews I talked about it to prove I had relevant experience, not to mention initiative and eventually with only one week before term was due to restart I got that work placement.</p><p>Fast forward to my final year (2004–05), and in January/March, I sent out a mail merge to around 30 different Manchester, Cheshire and nearby web agencies informing them of who I was and that I was graduating in six months. Nothing much happened; I might have got three emails all of which said, <em>thanks but they weren’t interested just now</em>. In hindsight, I would not advise this blanket approach. A better approach is to research 3–5 places you’d like to work then target them specifically. A mail-merge letter comes off as a bit cold which was something I did not appreciate when I was looking for my first job 12+ years ago.</p><p>Closer to graduation, I put my CV online with large job websites (the kind you see advertised on TV) and started applying for jobs — still nothing. With one month to graduation, I put my CV on local digital industry website, <a href="http://www.manchesterdigital.com/">Manchester Digital</a>, and I received an email which eventually lead to my first job at JJB Sports in their Marketing department. By spreading myself out and trying different techniques I found one that actually worked!</p><h3>How you can get your first job</h3><p>it’s ahrd to gauge if someone would be good at a job if they</p><ul><li>don’t have a web presence e.g. a website/blog/online portfolio/github (or equivalent) or a twitter account</li><li>have no relevant experience or references on their CV</li></ul><p>The last point is a big one. Experience is everything in this industry. You can get very far very quickly with no qualifications, if, that is, you have the requisite skills. A good education is brilliant but if the person in competition with you for a job has a year of experience on their CV and you only have a degree then the experienced person looks better (in most cases).</p><p>You have to get your name out there, so apply for jobs, <a href="http://twitter.com/imgiseverything">talk on twitter</a>, <a href="http://www.meetup.com/">try to network</a>, try to learn some important people’s names. Everyone in this industry knows everyone else therefore, if you apply to agency X and don’t get the job but you impress someone then an employee working at agency X might tell their friend working at agency Y about you.</p><h3>Networking</h3><p>Ah that dreaded word. A lot of (but definitely not all) developers are introverts and the thought of networking, strikes fear into them (it certainly does for me). However, there is a difference between traditional networking events (think walking into a large hall with people in suits and starting conversations with these people, who you don’t know, about work stuff) and merely getting to know people in the industry a little through Twitter, email, or having a casual chat at a design/dev talk like <a href="http://www.frontendlondon.co.uk/">Frontend London</a>.</p><h3>Getting the experience</h3><p>If you have no experience and therefore no commercial references, you should make it your mission to obtain some. If I were in that situation (again) I’d be looking to:</p><ul><li>set up my own website/blog</li><li>set up a website for a friend’s/relative’s small business (and get paid for it)</li><li>work for free* (or low pay) in a local web agency — making tea if I had to</li><li><a href="http://imgiseverything.co.uk/articles/junior-web-developer-salary/">take a lower paid (than expected) job as web developer</a></li><li>work for a local web agency — not as a web dev but maybe in a different role and work my way up</li><li>read books/blogs and practice web development as much as possible</li><li>make some money while waiting for that dream web development job</li></ul><p>If you apply for a job with no commercial experience, but you have built your own website then you’ll instantly look much better than your competitor who has no experience and no website.</p><p>* Point of note about working for free. Working for free to get experience is a good idea but don’t do it for too long. 1–2 weeks is fine <em>if you can afford it</em>. If an agency wants you to work for 1–3 months for no pay then they are most likely taking advantage of you and the chances are there is another agency somewhere willing to pay you to do the same job.</p><h3>Summary</h3><p>All web agencies are looking for people, and crying out for good junior web developers but they just can’t find them. Your mission is to seek out these people and let them know you exist and how good you are. You’ll save them time and money on advertising for people and you’ll save them from have to deal with recruitment agencies because they loathe that exercise.</p><p>By no means am I an expert on employment; these are just my experiences and advice. You may be a student on a fantastic university/college course teaching you everything you need to know :)</p><p>If you’ve got an experience or some advice on getting that first job that you’d like to share; I’d love to hear it.</p><p><strong>This post was first published in January 2009 at </strong><a href="http://imgiseverything.co.uk/"><strong>&lt;img /&gt; is everything</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=289d075fac86" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 speedy tips to optimise your web images]]></title>
            <link>https://medium.com/@imgiseverything/images-are-one-of-the-biggest-buzzkills-for-download-speeds-on-the-web-205e6c19daf9?source=rss-40c32f576127------2</link>
            <guid isPermaLink="false">https://medium.com/p/205e6c19daf9</guid>
            <category><![CDATA[svg]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[responsive-images]]></category>
            <dc:creator><![CDATA[Phil Thompson]]></dc:creator>
            <pubDate>Thu, 31 Aug 2017 15:55:05 GMT</pubDate>
            <atom:updated>2017-08-31T15:57:15.052Z</atom:updated>
            <content:encoded><![CDATA[<p>Images are one of the biggest buzzkills for download speeds on the web.</p><p>If your designer wants to use a carousel you’re potentially asking your customers to download several HUGE images and wait several seconds before they can interact with your site.</p><p>With the following 3 tips you could significantly improve your user’s download speeds and reduce their data bills without impacting the quality of your images. That’s win-win — right?</p><h3>1 Optimise your images in Photoshop/Illustrator</h3><p>Images are a killer on the web. We all want images to look crisp but what if we could have great looking images at smaller file sizes.</p><p>The biggest mistakes is when designers save images at 100% quality, when something like 75% will not reduce appearance but will dramatically reduce file-size.</p><h3>Here’s how</h3><ol><li>Trigger Save for Web by pressing Command-Option-Alt-s (on Mac)</li><li>Choose JPEG from the dropdown</li><li>Set Quality to Very High or 75%</li><li>Tick the Progressive box</li><li>Untick the Convert to sRGB box</li><li>Click Save…</li><li>Finally, run the saved image through an optimisation app like <a href="https://imageoptim.com/">ImageOptim</a></li></ol><h3>Here’s some screenshots of the process</h3><p>Option one is to save the image with Photoshop’s default Save As feature. You can optimise it in here but it’s not as obvious what you’re getting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/338/0*-fFAxFIyQI20JvB1.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/0*IXeMfcYpjL_oOD9C.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/442/0*KpjCWjc2qXAoe-22.jpg" /></figure><h3>Use mobile-sized images</h3><p>Mobile phones are only 300px to 600px wide so why are we sending them the same 1600px wide images that a 1920px wide desktop gets?</p><p>With HTML’s new &lt;picture&gt; element, we can now send different sized images to differently sized devices. We can even art direct imagery so your website’s mobile version can get a differently proportioned image and not just a scaled down one.</p><p>On a recent project with <a href="http://imgiseverything.co.uk/work/economist-films/">The Economist</a>, there was a need to display different images at different screen sizes — not just to give user’s on mobile a smaller image to download, but because the design was split into differently sized modules with copy laid on top of images and some call to action buttons laid on top of the image too. The images were 600px high (in the largest module) but as the screen got smaller, the images needed to stay the same height but shrink in width.</p><p>As the images in question were cover images for short films it wasn’t good enough to crop the image with CSS and risk a face or important part of the image being out of frame so different images were cropped at different sizes.</p><h3>Here is a sample of the code used:</h3><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/16aaa4ebbc0dd0e3bc67063045bf87ee/href">https://medium.com/media/16aaa4ebbc0dd0e3bc67063045bf87ee/href</a></iframe><p>Here we can see, that by default, a 312px wide by 600px high image is shown. Any browsers without &lt;picture&gt; support (and for whatever reason no JavaScript support) will get this image. Not the end of the world. We can size this with CSS so it’s full screen — which would make it blurred but it’s not a completely terrible fallback.</p><p>Then as the screen gets wider a wider image is displayed. Any screen wider than 321px gets a 471px wide image; anything wider than 471px gets a 632px wide image and anything larger than 632px gets the 961px wide image.</p><p><em>(N.B.The sizes 312px, 471px, 632px and 961px are merely the sizes in the design.)</em></p><p>The reason we set the first rule to be 321px is because an iPhone 5 is 320px wide so it’s a reasonable breakpoint, but more importantly — when the site’s gutters (of 10px either side of the image) are considered, a 312px wide image fits in the layout without any distortion. Each time the screen width becomes greater than the current image width we swap it with a wider image so user’s always get a crisp image.</p><p><strong>N.B.</strong> The picture element is not 100% supported across all browsers (as always, check <a href="http://caniuse.com/picture">caniuse.com</a> for details) so you may need some JavaScript to get it to work. That’s where the <a href="https://scottjehl.github.io/picturefill/">picturefill</a> script comes in.</p><h3>3 Use SVGs</h3><p>SVG may be a new term to a lot of people but it’s likely your design team is already creating vector graphics as part of their process. Create a logo or icon in Illustrator and saving as a .eps or .ai file makes it automatically a vector. <a href="https://helpx.adobe.com/uk/illustrator/how-to/export-svg.html">So exporting it as an SVG is super easy</a>.</p><p>Little things like using SVGs instead of PNGs/JPGs for icons and logos can go a long way to making your website look slicker.</p><p>Sick of maintaining 2x or 3x size images for retina devices? Switching to SVG means you don’t have to anymore — an SVG looks crisp on any device and it’s easy to animate too.</p><p>A few years ago, developers would place all their icons inside sprites (i.e. one big image containing smaller images) but this is no longer the optimal approach — SVG is!</p><p>You can even optimise SVGs by running them through an app like <a href="https://jakearchibald.github.io/svgomg/">SVGOMG</a> to remove whitespace and shrink the file-size further.</p><h3>SVG Sprites</h3><p>Okay, so sprites haven’t gone away, they still make sense except now we have SVG sprites instead of giant PNGs. Inline SVGs make a lot of sense; you can animate them and manipulate them in many ways, but say you have a table with 30 rows and each row has a delete icon and an edit icon. It would be silly to repeat each SVG 30 times.</p><p>The solution is to put all your SVGs in one big SVG file (e.g. a sprite) as &lt;symbol&gt;s and reference your SVG like so:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e8264c465dbd10468aaf824916070150/href">https://medium.com/media/e8264c465dbd10468aaf824916070150/href</a></iframe><p>That’s great but it doesn’t allow browsers to cache the sprite (and therefore have quicker repeated views of your website) and it adds a lot of bloat to the HTML.</p><p>Don’t fear help is on the way, because you can simply reference an external SVG file instead of the one inline in HTML. You’d simply edit the &lt;use&gt;‘s xlink:href attribute value to have a full href value like /assets/path/to/sprite.svg#icon-close instead of #icon-close.</p><p>External SVG sprites aren’t 100% supported (big surprise) so you may need some JavaScript (again) in the form of a script called <a href="https://github.com/jonathantneal/svg4everybody">SVG4Everybody</a> to get it working in all the (currently) modern browsers.</p><h3>Summary</h3><p>Those fixes can be made today and your website’s visitors will be happier if you use them on your site.</p><p><strong>This article was first published in March 2016 on </strong><a href="http://imgiseverything.co.uk/articles/optimise-web-images/"><strong>&lt;img&gt; is everything</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=205e6c19daf9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A freelancer’s 10 step guide to getting paid (on time)]]></title>
            <link>https://medium.com/@imgiseverything/a-freelancers-10-step-guide-to-getting-paid-on-time-c20bb9544e2f?source=rss-40c32f576127------2</link>
            <guid isPermaLink="false">https://medium.com/p/c20bb9544e2f</guid>
            <category><![CDATA[invoice-freelancer]]></category>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[pay]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[freelancing]]></category>
            <dc:creator><![CDATA[Phil Thompson]]></dc:creator>
            <pubDate>Thu, 31 Aug 2017 14:40:20 GMT</pubDate>
            <atom:updated>2017-08-31T14:40:20.114Z</atom:updated>
            <content:encoded><![CDATA[<p>As a freelancer, getting paid on time is absolutely crucial and yet, the attitude amongst some freelancers is that getting paid late (or <em>not at all</em> in some circumstances) is beyond their control. It isn’t.</p><p>So how do you ensure you get paid on time, almost every time? Well, it’s not easy. I myself get paid late quite often. I work with digital agencies, who are bigger than me (anywhere from 2 to 100 employees) so they often dictate the payment terms — which are usually <a href="http://en.wikipedia.org/wiki/Net_D">Net 30 days</a>. More often than not, they pay on time, sometimes early and sometimes a little after those 30 days.</p><p><strong>Caveat:</strong> I work with digital/design/marketing agencies; I go to them direct and I do not work with recruitment agencies or umbrella companies who often have their own payment structure in place. I do sometimes work with direct clients and I have found these tips work well with them too, but I don’t tend to work with very large corporations (so these tips may not work for you if large businesses are your target market).</p><h3>1. Talk about money at the start</h3><p>Do not be shy when it comes to talking about money. When someone comes to you and requests that you do some work for them, if they don’t ask what your rate is make sure they are aware of it. You do not want a situation where they try to renegotiate your rate mid-way through the job or there’s a miscommunication and they assume (whether on purpose or by accident) your rate is lower than it is.</p><p><strong>Sidenote:</strong> Personally, I have a rates page on this website and when someone asks about my rates I point them to that page. It details my rates and discounts I provide for longer term projects. Since creating this page, fewer clients have tried to negotiate down my rates.</p><p>Ask them what their payment terms are before agreeing to work with them. Will they pay you a deposit upfront? Will they pay after 30 days of you invoicing them? Will they pay when <em>you</em> finish <em>your</em> part of the project or will they wait for the <em>overall</em> project to be completed? Will they only pay you once their client pays them? Will they pay weekly/fortnightly/montly?</p><p>See that last one ‘<em>they only pay you once their client pays them</em>’ this is your cue to run a mile. When <em>they</em> get paid is of no concern to <em>you</em>. You have no idea how good their team is at getting their invoices paid so do not agree to this. Good clients have good cashflow.</p><h3>2. Don’t be afraid to negotiate</h3><p>A client will often try and negotiate down your rate. You can say no but if they’re quite insistent and you <em>need</em> the work you may be able to get them to give you better payment terms for that discount. Remember £400 in your bank account now is better than £450 in 2–3 months time. Anything could happen in that 2 months: they could go bankrupt for instance.</p><p>Remember, you are perfectly entitled to request any of the following:</p><ul><li>For them to pay you a certain way e.g. bank transfer instead of cheque</li><li>For the payment terms to be reduced from 90 days to 60 days or from 30 days to 15 days.</li><li>For them to pay a (non-refundable deposit) or in staged payments</li></ul><p>They can say only no.</p><p>If the project length is quite long say 2 or 3 months or more then ask to invoice for your time monthly or maybe even weekly. You don’t win any prizes for invoicing at the end of a 3 month contract. This is as bad for your client’s cash flow as it is for yours.</p><p><strong>Sidenote here:</strong> I’ve often found that people looking to get your rate down aren’t that reliable at paying on time. This is not a <em>strict</em> rule, but at this point if you get a funny feeling about the (potential) client then really think about whether this job is worth it.</p><h3>3. Find out what the process is for invoicing</h3><p>Who do you send invoices to? The Traffic Manager who booked you? The Accounts Department? Is it a specific person? Maybe it’s Alex in Accounts? Who is it? Try and get their email address and/or direct line phone number. Then ask them some questions, number one being <em>Do you need a PO (Purchase Order) number in order to start work?</em></p><p>Sometimes you will and sometimes you won’t, but if you do need one and they haven’t given you one you may find that your invoice payment is delayed. PO Numbers represent a little bureaucracy and sometimes not having one, means a senior finance person hasn’t signed off your project/your costs and internal politics may cause your invoice payment to be delayed or not paid at all.</p><p>Double check with this person what the payment terms are; if you’ve negotiated with someone to get different (better) payment terms than this person is used to then make sure with them that that has been signed-off. In the past I’ve negotiated from 60 days to 30 days at large agencies only to find that the person who negotiated that rate hadn’t asked the Finance Director, they’d just assumed it would be fine, so I got paid after 60 days.</p><p>Ask this person what information you’ll need to invoice them — how do <em>they</em> like the invoice to be? What information do <em>they</em> need to do their job properly and efficiently.</p><p>You know when someone gives you a PSD and every layer is called <em>Layer 1 Copy</em>. Guess what? That’s you when you send the Accounts team (who are pretty busy and stressed) an invoice missing the key information that they need.</p><h3>4. Make friends with key people</h3><p>You know who is easy to not pay, that freelancer who is a jerk. Be polite, friendly and useful in all correspondence with people in the team. If Accounts decide to delay your invoice (because sometimes their job is to <em>not</em> pay your invoice for as long as possible because their clients are doing the same thing to them) you want a champion inside the business who goes to Alex in Accounts and says ‘<em>Hey! please pay Phil, he did a good job and I want to work with him again.</em>’.</p><p>Hopefully, the way you spoke to the Alex from Accounts in step 3 has warmed them to you and they’ll be happier to pay you. Perhaps when they’ve got two invoices that have come in at the same time, and they need to hold on to some of their cash flow they’ll pay your invoice first because you were helpful and nice.</p><h3>5. After the job has finished, invoice and check the invoice has been received</h3><p>You would not believe how many freelancers forget to invoice. I’ve been guilty of this in the past too. The job finishes and you start on the next job; a week whizzes by and you realise that you forgot to send your invoice. Oops, that’s another week without getting paid. Those 30 days only start when you send the invoice and no sooner.</p><p>We’ve all been told that the invoice was <em>never received</em> when it comes to the due date, but you can prevent that excuse by asking Alex from Accounts to confirm that they received it. If your invoicing app gives you a notification that they’ve received/opened the email then email Alex from Accounts separately anyway. Ideally, you want the person to respond, saying ‘<em>yes I got it and it’s got all the information I need on it and it will be paid on this 2nd of Whenever</em>’.</p><h3>6. Remind them it’s coming due</h3><p>A week before the invoice is due, send Alex from Accounts an email letting them know the invoice is due and ask them when you should expect payment. Will it be on time? Remembering to be polite, the invoice isn’t late yet so be nice.</p><p>The Accounts team may only pay invoices once a month — the so-called payment run. By this point you should know enquire when the next payment run is and if your invoice is on it.</p><h3>7. Remind them it’s due</h3><p>On the due date remind them it’s now due and and ask them when you should expect payment. Will it be on time? Yes this step is the same as the one before so if you feel like you’re annoying them, stop thinking like that; you did a job (a good one I hope) and you deserve to be paid.</p><p>Alex from Accounts might have 5 invoices to pay and only enough cashflow to pay 4 of them. Being nice but being firm might mean you are one of the 4 invocies that get paid.</p><h3>8. Remind them it’s overdue</h3><p>Hopefully you got paid by now but maybe you didn’t, so remind them again. Be polite but be firm. State the facts, explain that the invoice is overdue, by <em>x</em> days. Maybe attach the invoice to the email so they can’t say they haven’t got it/can’t find it.</p><h3>9. Still not paid? Ask why not and negotiate</h3><p>In my experience, it’s rare for someone to not pay at all. Some people aren’t very nice, but most people want to pay… so if the invoice is really quite late, ask why it’s been delayed. Maybe it’s a legitimate reason. Maybe they’re short on cash themselves. If they’re genuine, then you acting unprofessionally will do nothing but damage your reputation so be nice and try to be understanding. If they are struggling for cash flow you could offer them an extension or offer to accept a percentage of the overdue amount now and the rest in say another 30 days.</p><p>That may be the difference between getting paid a bit and not getting paid at all.</p><h3>10. Still not been paid?</h3><p>Something that has worked for me in the past is to turn up in person and ask for the money. You’d be surprised how often this works. I once freelanced at an agency where the MD only paid freelancers if they came in to the office, in person, and asked for it and he’d write them a cheque there and then.</p><p>Ring them up and tell them you’re passing by that day and you can pop in and pick up your cheque. You’d be surprised how often it’s waiting for you when you get there.</p><h3>11. Bonus tip. Don’t do this</h3><p>I’ve read a lot of people saying, make sure you have a contract that stipulates you’ll charge interest on the invoice if it’s overdue. By all means, use a contract and put this clause in there, but it’s not really enforceable; the type of client who won’t pay your invoice won’t pay you 5% interest per day it’s late either. In my experience, people who offer this advice rarely do it themselves — so take it with a pinch of salt.</p><h3>Summary</h3><p>It’s hard to follow these steps; I sometimes forget one or two of them. Especially step 4 but in over 9 years freelancing I have only ever not been paid once and have only wait a really long time (over 6 months) once — so this process does work.</p><p>The best tip for getting paid on time is to not work for people if they mess you about. If they’re late with payments don’t work with them again and as mentioned in step 2; sometimes you’d get a feeling in the early stages that the client might not be very good at paying you. I’d urge you to go with this instinct, in my experience it’s often correct. I’ve never regretted turning down a job after having this feeling, but I <em>have</em> regretted ignoring my gut instinct many a time.</p><p>I want to leave you with one piece of advice. Make sure you get paid. It’s tricky as a freelancer (especially doing a job you love) because you can feel like you’re overcharging, you can feel like you’re bothering people or being cheeky by asking for money but you’re not; you’ve completed the work, you’ve earnt that money so make sure you get it.</p><p>Ask yourself this, if you’ve ever hired a plumber, builder, or a carpenter — how did they ask to be paid? Would you have thought it was acceptable to get them to do the job, agree to pay them at the end of the day/week then, when that time came you’d ignore their calls or tell them ‘<em>oh sorry, I’ll pay you at the end of next week</em>’. I hope you wouldn’t treat people like that so don’t let clients treat you like that.</p><p><strong>This article first appeared in 2015 on </strong><a href="http://imgiseverything.co.uk/articles/freelancers-guide-getting-paid-10-steps/"><strong>&lt;img is everything&gt;</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c20bb9544e2f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My experience of becoming a Lead Front-end Developer for the first time]]></title>
            <link>https://medium.com/@imgiseverything/my-experience-of-becoming-a-lead-front-end-developer-for-the-first-time-ba8ef01a2c8e?source=rss-40c32f576127------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba8ef01a2c8e</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Phil Thompson]]></dc:creator>
            <pubDate>Wed, 30 Aug 2017 15:03:44 GMT</pubDate>
            <atom:updated>2017-08-30T15:03:44.440Z</atom:updated>
            <content:encoded><![CDATA[<p>On project last year, a month after starting, I was promoted into the role of Lead Developer, in charge of 3, and at times, 4 other developers in the dev team. This was the first time I’d been the Lead Developer on a project (where I was <em>not</em> the sole developer as well). The project ran for 6 months in total and I learnt a lot in the process.</p><h3>The core job description of the Lead Developer on this project was:</h3><ul><li>Assign tasks to the 3–4 other developers</li><li>Monitor the progress of those tasks and feedback to Project Managers (PMs), Account Managers (AMs) and other non-dev team members</li><li>Try to maintain code-quality <em>e.g. review Pull Requests (PRs), provide feedback to devs and approve/deny PRs</em></li><li>Merge PRs into main code branch and deploy to staging/production environment</li><li>Be the voice of the dev team if there are any disputes about the work e.g. scope creep, unrealistic timelines</li><li>Carry messages from non-dev team members <em>e.g. PMs to the dev team</em></li><li><em>Have the final say on coding decisions</em></li><li>Presenting code demos to non-dev team members</li><li>Keep (Quality Assurance Testers) QAs aware of progress AND finally</li><li>Continue coding as usual</li></ul><p>Okay, so, the last task is the hardest. When you are reviewing the PRs of 3–4 other devs towards the end of the sprint, trying to motivate them, trying to communicate their workload and your expected finishing times to PMs whilst trying to manage your own work was very stressful at times.</p><p>However, what I did enjoy was having some semblance of control over the final product and being able to say ‘<em>we have coded this like that because of XYZ</em>’ and presenting that to UX/AM/PMs and generally being believed/respected.</p><h3>Trying to maintain code quality</h3><p>It was also incredible difficult to maintain code quality and speed of other developers; I wasn’t really prepared for this. When the deadline is looming and everyone is behind, it became impossible to justify spending time enforcing specific coding guidelines like spaces before curly braces in JavaScript or alphabetised CSS rules and minimal nesting in Sass or that elements were exactly 20px apart or that the font size was supposed to be 11px and not 12px.</p><p>If I’d have had more time and more foresight I would have ruled with more of an iron fist in the beginning of the project which I feel would have prevented problems with the code further down the line. However, as I joined the team after coding had been started and I was then promoted after some code had already been written (in multiple styles), it did not feel practical to start refactoring every code after I became the lead. Nor was there the time.</p><h3>Documentation &gt;= code</h3><p>Code is really important but keeping track of the code, documenting it and letting non-dev people know what’s going on is even more important. At the start, we were pushing, pulling and merging and trying to get our commit messages as good as possible, but when you pass that code on to a third party (or when you have a gap inbetween finishing the code and releasing it) you realise that you can’t remember exactly what has been changed and why.</p><p>Maybe 2 new functions have been added and 1 has been removed but why and what modules/pages etc does it affect? Why was the decision made to make those changes? If you don’t write it down someone will either override your changes later in the project because they don’t understand why a decision has been made or the end-client/non-dev team member will request a change that requires significant work because they do not understand the background.</p><h3>Managing developers</h3><p>Same goes for other developers, writing code when you are the sole developer is a very different proposition from writing code that a team of other developers have to understand, extend, delete, or upgrade. And part of the job of the Lead Developer is diplomatically trying to get all developers to appreciate this without causing offence — this was something I did not excel at, at first, and I admit that I found it quite uncomfortable trying to explain to developers (who had been on the same level as me at the start of the project) that they needed to improve. I like to think this is something I improved upon as the project wore on, but that is for others to decide.</p><h3>Agency development life</h3><p>If you don’t work in an agency, it may be hard to understand how/why you have to make compromises on code quality. Every sprint (i.e. 2 week block of work) is timed and justified by the price paid by the client; if you slip on these deadlines and start falling behind the agency starts losing money.</p><p>It can be hard to justify to an agency that up-front costs are needed that may save costs down the line (e.g. setting up automated JavaScript testing, or properly planning all modules/components that the system will use before starting to code) because it’s hard to explain this to the end-client who just wants you to start coding and producing work straight away.</p><p>In different environments there isn’t always the same time-pressure and more of a focus on quality over speed can be used.</p><h3>Occasional Tech Lead responsibilities</h3><p>At times, when the Tech Lead was otherwise unavailable, I was also asked to take on some of their responsibilities for this project which included:</p><ul><li>Estimating development time based upon initial UX wireframes (this was prior to sprint planning with other devs where the timings were refined)</li><li>Reviewing the end-client’s bugs and estimating time required to fix, whether bugs were really bugs or disguised scope creep</li><li>Feeding back to the end-client on bug fixing status</li></ul><h3>Summary</h3><p>I was very grateful for the opportunity of stepping up to be a Lead Developer on this project and whilst my next role will <em>only</em> be a Senior Developer and <em>not</em> a Lead I will be looking to be a Lead Developer again as soon as the opportunity arises.</p><p>I worked with some great people on this project and while at times the project was a slog, it was often a joy to come into work and spend time working with them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba8ef01a2c8e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>