ianfeather.co.uk Report : Visit Site

Technical data of the ianfeather.co.uk

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host ianfeather.co.uk. Currently, hosted in United States and its service provider is Google Inc. .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called Netlify containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

engineering at buzzfeed twitter github radical candor in code review written on 17 march 2018 | comments recently i read radical candor by kim scott . it discusses how we can communicate more directly and effectively and it’s something buzzfeed have integrated into our culture. i find myself looking for more opportunities to give direct feedback to my colleagues, both positive and negative, where previously i would have shied away. kim defines radical candor as: radical candor™ is the ability to challenge directly and show you care personally at the same time. both of these sides are crucial. if you just challenge directly but don’t care about the person then you come across as an asshole. if you care but aren’t prepared to offer any guidance then you’re not helping that person. to emphasise this point she designed the following diagram: she explains the other three quadrants (taken from radicalcandor.com ): obnoxious aggression™ is what happens when you challenge but don’t care. it’s praise that doesn’t feel sincere or criticism that isn’t delivered kindly. ruinous empathy™ is what happens when you care but don’t challenge. it’s praise that isn’t specific enough to help the person understand what was good or criticism that is sugarcoated and unclear. manipulative insincerity™ is what happens when you neither care nor challenge. it’s praise that is non-specific and insincere or criticism that is neither clear nor kind. what does this have to do with code review? the book is written for people in leadership positions but the lessons are universal. fundamentally it’s about helping those around you be as successful as they can be. as developers we rarely exist in a silo so communication is one of the most important tools we have. i’ve seen a lack of empathy for someone else’s opinion cause serious rifts within a team and this happens more than ever during code review, usually as comments on pull requests. so let’s look at how we can apply radical candor to code review. obnoxious aggression these are the type of pr comments that stick in our minds, go viral on twitter, and are typically deemed as being from ‘assholes’. a real one that sticks in my mind was a single comment on a large pull request: lodash templates blow. it’s crass, it’s unconstructive. it was followed by the commenter rewriting the pr (without asking) to use a different templating language. it was also followed by the author of the original pr looking for a new job. manipulative insincerity this can transpire in lengthy prs where someone only adds a single lgtm comment. unless it’s been discussed offline it’s likely that the reviewer simply doesn’t care enough to invest their time in thoroughly reviewing the code. in this case their approval is both hollow and disrespectful. if you actually do come across a long pr with no faults whatsoever you should take the opportunity to offer some more constructive, positive feedback. in its worst form this can also be represented by a lack of a comment. the reviewer sees something they know is risky but they keep quiet, perhaps thinking that the author will learn their lesson when it causes them problems later on. ruinous empathy you may be hitting this area if you try to sugarcoat some negative feedback for fear of hurting the feelings of the author. pay attention to your use of “could”, “maybe”, “if you like”, “up to you”, particularly if your real feelings about it are stronger. this can also be an issue when re-reviewing code: if the author has improved their code in response to a number of your comments but it still doesn’t reach the standard it should be at. it’s possible you will look for ways to praise their improvements rather than make further direct feedback. what does the radical candor version look like? give positive feedback take time to acknowledge the good parts and comment if you learned something. this is something we often overlook because we become trained to simply spot defects. take time to guide the person, not just the code this is about explaining the “why”. what was it you experienced/read/told that gave you the different perspective? share those resources. use facts/experience rather than opinions “i don’t like this pattern” vs “this pattern actually caused us issues in a previous project because of x”. use non-threatening language some people might be ok receiving feedback that borders on obnoxious aggression but they are likely to be in the minority. it can also be intimidating for others who see those comments. understand your own personality and act accordingly my natural tendency is to be over polite and hold back if i don’t know the author that well. because of that, if i doubt myself i typically err on the side of saying something. you might want to consider erring on the side of holding back if your personality is the opposite. removing legacy globals with es6 proxies written on 27 july 2017 | comments i found a nice pattern today for getting rid of those global configuration variables that you’re pretty sure aren’t used anymore but you’re a bit too scared to delete. you know the ones, they look like this: /* do not change! will break something somewhere. trust me. thx. */ window.global_config = { env: 'dev', ... } they’re the cockroaches of large sites: they outlast developers, framework apocalyses, full rewrites. you know that something outside of your code base relies on them and it’s near impossible to figure out what. it’s easier to just leave it where it is and move on with your life. well, es6 proxies actually make it a whole lot easier to find out which properties aren’t being used! proxies allow you to put logic between someone trying to access a property and them actually receiving it. here’s some actual code: (function() { /* first we'll rename our `global_config` object and make it private */ var _config = { env: 'dev' }; /* if we don't support proxies let's just give them what they want! */ if (!('proxy' in window)) { window.global_config = _config; return; } /* * alright, now we make a proxy object. * * get is a function that will be called every time we access * a property. * * at this point, all we're going to do is return the original value. */ var myproxy = { get: function(target, name) { return _config[name]; } }; /* finally, let's assign it back so there's no difference for the consuming code. */ window.global_config = new proxy({}, myproxy); }()); and we’re done! we’ve written some code which does absolutely nothing! var x = window.global_config.env; console.log(x); // log: "dev" this is usually where i’d stop but in fact it gets a bit more fun when you add some logic to the myproxy object. for example we could log out which properties have been called: var myproxy = { get: function(target, name) { console.log(`someone tried to access global_config.${name}!`); return _config[name]; } }; var x = window.global_config.env; // log: someone tried to access global_config.env! console.log(x); // log: "dev" reloading the page might give you some idea of who is accessing the object but, given that the calling code is probably outside of your own code base, it’s only going to get you so far. instead, let’s send that data somewhere! your favourite analytics service will probably do the trick. var myproxy = { get: function(target, name) { // assume this method makes a http request somewhere track('global_config', name); return _config[name]; } }; now just deploy it for a bit and let your users tell you which properties are still being accessed! you might end up with some graphs like this: and now we can delete the base_url property, safe in the knowledge that no one is using it. destructuring, rest properties and object shorthand written on 11 january 2016 | comments destructuring and rest/spread parameters for arrays is part of the es6 specification. support for their use with objects is, at the time of writing, a stage 2 proposal for future inclusion . of course, you can use it today via a transpiler

URL analysis for ianfeather.co.uk

https://www.ianfeather.co.uk/non-tech/preparing-for-the-utmb-occ/
https://www.ianfeather.co.uk/what-even-is-vanilla-js-these-days/
https://www.ianfeather.co.uk/communal-momentum-and-accountability/
https://www.ianfeather.co.uk/destructuring-rest-properties-and-object-shorthand/#disqus_thread
https://www.ianfeather.co.uk/posts
https://www.ianfeather.co.uk/destructuring-rest-properties-and-object-shorthand/
https://www.ianfeather.co.uk/what-even-is-vanilla-js-these-days/#disqus_thread
https://www.ianfeather.co.uk/voting-with-your-wallet/
https://www.ianfeather.co.uk/radical-candor-in-code-review/
https://www.ianfeather.co.uk/fewer-words
https://www.ianfeather.co.uk/radical-candor-in-code-review/#disqus_thread
https://www.ianfeather.co.uk/radicalcandor.com
https://www.ianfeather.co.uk/non-tech
https://www.ianfeather.co.uk/removing-legacy-globals-with-es6-proxies/#disqus_thread
https://www.ianfeather.co.uk/removing-legacy-globals-with-es6-proxies/
amazon.co.uk

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Error for "ianfeather.co.uk".

the WHOIS query quota for 2600:3c03:0000:0000:f03c:91ff:feae:779d has been exceeded
and will be replenished in 18552 seconds

WHOIS lookup made at 02:05:29 15-Jun-2017

--
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:

Copyright Nominet UK 1996 - 2017.

You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at http://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

  REFERRER http://www.nominet.org.uk

  REGISTRAR Nominet UK

SERVERS

  SERVER co.uk.whois-servers.net

  ARGS ianfeather.co.uk

  PORT 43

  TYPE domain

DISCLAIMER
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:
Copyright Nominet UK 1996 - 2017.
You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at http://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

  REGISTERED no

DOMAIN

  NAME ianfeather.co.uk

NSERVER

  NS1.UKSERVERS.NET 217.10.138.210

  NS3.UKSERVERS.NET 104.236.242.132

  NS.UKSERVERS.NET 128.199.238.210

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .