<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for kernowsoul</title><link>http://disqus.com/by/kernowsoul/</link><description></description><atom:link href="http://disqus.com/kernowsoul/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 03 Apr 2020 10:57:20 -0000</lastBuildDate><item><title>Re: 4 Ways to Avoid Merge Commits in Git (or How to Stop Being a Git Tit)</title><link>http://kernowsoul.com/blog/2012/06/20/4-ways-to-avoid-merge-commits-in-git/#comment-4859388323</link><description>&lt;p&gt;Avi, the response I posed here answers a similar question &lt;a href="https://kernowsoul.com/blog/2012/06/20/4-ways-to-avoid-merge-commits-in-git/#comment-1373367197" rel="nofollow noopener" target="_blank" title="https://kernowsoul.com/blog/2012/06/20/4-ways-to-avoid-merge-commits-in-git/#comment-1373367197"&gt;https://kernowsoul.com/blog...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Fri, 03 Apr 2020 10:57:20 -0000</pubDate></item><item><title>Re: [object Object]</title><link>https://staging.clubhouse.io/blog/fix-errors-faster-clubhouse-sentry-integration#comment-4444931449</link><description>&lt;p&gt;Great that the integration is 2 way now!&lt;/p&gt;&lt;p&gt;The new integration appears to create clubhouse stories as features rather than bugs and I can't see any way of changing this.&lt;/p&gt;&lt;p&gt;Other features that would be super useful:&lt;br&gt;* Being able to select the state of the story being created and setting a default. We have a "Triage" state we use for incoming bugs&lt;br&gt;* Being able to set a default template for the story description&lt;br&gt;* Being able to set default labels for stories&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Wed, 01 May 2019 05:51:38 -0000</pubDate></item><item><title>Re: Shipping React Native apps with Fastlane</title><link>http://carloscuesta.me/blog/shipping-react-native-apps-with-fastlane/#comment-4125313972</link><description>&lt;p&gt;@Martin Abanes from what I understand you have to run `fastlane init` within the ios folder. Once it's done it's stuff you can move the files to the top level but you have to specify the paths in some of the commands that are run as fastlane expects to be run from inside the ios or android folders by default&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Tue, 02 Oct 2018 11:51:09 -0000</pubDate></item><item><title>Re: 5 arch supports and why your cycling feet need them</title><link>https://www.bikeradar.com/road/gear/article/arch-supports-for-cyling-52752/#comment-4044804395</link><description>&lt;p&gt;Superfeet are also an option worth considering&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Fri, 17 Aug 2018 02:44:40 -0000</pubDate></item><item><title>Re: How to Rumble like a boss - KernowSoul</title><link>http://kernowsoul.com/blog/2013/10/16/how-to-rumble-like-a-boss/#comment-3090401429</link><description>&lt;p&gt;Thank you for the kind words&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Mon, 09 Jan 2017 07:18:14 -0000</pubDate></item><item><title>Re: 4 Ways to Avoid Merge Commits in Git (or How to Stop Being a Git Tit)</title><link>http://kernowsoul.com/blog/2012/06/20/4-ways-to-avoid-merge-commits-in-git/#comment-1373367197</link><description>&lt;p&gt;Merge commits have their place, if you follow a git flow style workflow &lt;a href="http://nvie.com/posts/a-successful-git-branching-model/" rel="nofollow noopener" target="_blank" title="http://nvie.com/posts/a-successful-git-branching-model/"&gt;http://nvie.com/posts/a-suc...&lt;/a&gt; then there are certain times when it's useful to have a merge commit in order to properly track history.&lt;/p&gt;&lt;p&gt;In day to day use merge commits are not good as they clutter the git history with unnecessary commits which have no explanation to indicate what the commit contains. If you consider that 2 people have changed the same file person A pushes their change, person B then pulls and has to resolve the conflict, if a merge commit is added the result is 3 commits, Person A's change, then Person B's change, then a merge commit to resolve a conflict. If a rebase is used Person B's original commit can be edited to resolve the conflict which results in just 2 commits, one from each person. In isolation this may not appear to be an issue having an extra commit but consider even a modest sized team of 5 people it can easily get out of hand to the point where the git history becomes very difficult to read.&lt;/p&gt;&lt;p&gt;Having lots of merge commits can make using some of the git tools rather more troublesome, for instance, if a bug is introduced and git bisect needs to be used.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Wed, 07 May 2014 07:47:57 -0000</pubDate></item><item><title>Re: How Our Startup Beat Burnout</title><link>https://www.groovehq.com/blog/burnout#comment-1294548565</link><description>&lt;p&gt;Surely is would be better to give your staff the day after their birthday off no?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Fri, 21 Mar 2014 05:52:25 -0000</pubDate></item><item><title>Re: 3 Things Freelancers Should Know About RFPs</title><link>https://doubleyourfreelancing.com/3-things-freelancers-know-rfps/#comment-1263157157</link><description>&lt;p&gt;I'm getting white text on a white background in chrome on the mac&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Thu, 27 Feb 2014 12:14:27 -0000</pubDate></item><item><title>Re: 2013 Rails Rumble</title><link>http://r13.railsrumble.com/entries/218#comment-1094121843</link><description>&lt;p&gt;Good work in the time frame, looks good too. Would be good to be able to insert reply templates from the KB or something along those lines.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Wed, 23 Oct 2013 15:09:51 -0000</pubDate></item><item><title>Re: 2013 Rails Rumble</title><link>http://r13.railsrumble.com/entries/399#comment-1094067970</link><description>&lt;p&gt;good work&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Wed, 23 Oct 2013 14:30:35 -0000</pubDate></item><item><title>Re: 2013 Rails Rumble</title><link>http://r13.railsrumble.com/entries/46#comment-1094027905</link><description>&lt;p&gt;Looks good, works well, easy and simple to use, well done. Handles more complex schedules like "2nd Thursday of every month". I like the duplicate feature, maybe that button should be on the index view as well.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Wed, 23 Oct 2013 14:01:43 -0000</pubDate></item><item><title>Re: 4 Ways to Avoid Merge Commits in Git (or How to Stop Being a Git Tit)</title><link>http://kernowsoul.com/blog/2012/06/20/4-ways-to-avoid-merge-commits-in-git/#comment-1047656491</link><description>&lt;p&gt;Dave, thanks for the comment, you are correct I will update the article shortly.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Tue, 17 Sep 2013 04:31:37 -0000</pubDate></item><item><title>Re: A knife.rb for our time - Automate All the Things!</title><link>http://dougireton.github.io/blog/2013/03/17/a-knife-dot-rb-for-our-time/#comment-966816460</link><description>&lt;p&gt;Thanks for sharing your knife config, looks like a good way to go. Is there a reason you have not included the validation_client_name and validation_key settings in the file?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Thu, 18 Jul 2013 08:01:29 -0000</pubDate></item><item><title>Re: 4 Ways to Avoid Merge Commits in Git (or How to Stop Being a Git Tit)</title><link>http://kernowsoul.com/blog/2012/06/20/4-ways-to-avoid-merge-commits-in-git/#comment-929112683</link><description>&lt;p&gt;Look like we have very similar setups, typing is over rated and who has time to type `it`!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Thu, 13 Jun 2013 10:00:22 -0000</pubDate></item><item><title>Re: 4 Ways to Avoid Merge Commits in Git (or How to Stop Being a Git Tit)</title><link>http://kernowsoul.com/blog/2012/06/20/4-ways-to-avoid-merge-commits-in-git/#comment-928745653</link><description>&lt;p&gt;I have something similar setup, I've aliased `git` to `g` and then have `pl` for `pull`. Interesting regarding the `r` for rebase, I have mine setup to always rebase for `g pl` which is what I use 99.999% the time, then if I run `g pull` it pulls without rebasing. Not obvious to others but then it's only me who uses the commands and if anyone else uses my machine the standard git commands work as expected.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Thu, 13 Jun 2013 04:46:18 -0000</pubDate></item><item><title>Re: The 2012 Winners Have Been Announced!</title><link>http://blog.railsrumble.com/2012/10/19/winners-announced/#comment-689084895</link><description>&lt;p&gt;@Thomas Muntaner having been on both sides of the rails rumble, both a competitor and this year a judge I can understand your frustration. From the judging perspective we had about 300 entries to look through in short space of time. Most of us will have full time jobs so are doing the judging in spare time. Getting through the entries can be quite a challenge but I think it's very realistic, real users will give your app a similar amount of attention.&lt;/p&gt;&lt;p&gt;I would consider this a learning experience rather than a negative experience. Things to consider for next time.&lt;/p&gt;&lt;p&gt;1. Make it as easy as possible to see all of your app.&lt;br&gt;2. Don't make users signup unless it's absolutely crucial. I saw a very large number of entries that required a signup that could have done without it.&lt;br&gt;3. If you do require users to signup create a dummy account already populated with data and provide the demo login on your apps profile or front page.&lt;br&gt;4. Personally I like facebook/twitter logins for entries as they are fast, just don't request more access than you need. I wouldn't give any app access to my github that has read/write access to repos, it's too dangerous, so forget about github authentication.&lt;br&gt;5. Create a short video/screencast that demonstrates your app.&lt;/p&gt;&lt;p&gt;You're trying to hook the judges in just like you would any member of the public. Anything that makes discovering the features of your app quicker and easier is going to get you more attention.&lt;/p&gt;&lt;p&gt;During a previous rails rumble worked in a team that created a table football stats app which generated all sorts of graphs from the stats. These stats were only generated after 3 match results were entered. Not one of the judges created more than 1 match so never got to see the statistic which was a large part of the app. We felt pretty disappointed after this but realised it was out own fault, we should have created a demo account with the stats already present and a video demoing the app for the front page.&lt;/p&gt;&lt;p&gt;In the end that fact that the judges didn't see our entire app didn't matter, we had fund doing taking part and we used the app for months within our company and got a lot of enjoyment out of it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Mon, 22 Oct 2012 07:13:20 -0000</pubDate></item><item><title>Re: 2012 Rails Rumble</title><link>http://r12.railsrumble.com/entries/173#comment-686475421</link><description>&lt;p&gt;Nice idea, simple, easy to use. Well done. Small issue, the document signing didn't work in my Sparrow mai client and there was no link to sign online. Worked using gmail though.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Thu, 18 Oct 2012 16:12:11 -0000</pubDate></item><item><title>Re: 2012 Rails Rumble</title><link>http://r12.railsrumble.com/entries/272#comment-686464795</link><description>&lt;p&gt;Takes me back to my childhood Top Trumps days. Good effort guys&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Thu, 18 Oct 2012 15:59:55 -0000</pubDate></item><item><title>Re: 2012 Rails Rumble</title><link>http://r12.railsrumble.com/entries/43#comment-684615458</link><description>&lt;p&gt;Great fun, as it turns out I don't know my friends very well. Well done guys.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Tue, 16 Oct 2012 18:02:45 -0000</pubDate></item><item><title>Re: 2012 Rails Rumble</title><link>http://r12.railsrumble.com/entries/61#comment-684611311</link><description>&lt;p&gt;Very slick interface, really like this. Well done&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Tue, 16 Oct 2012 17:58:32 -0000</pubDate></item><item><title>Re: iPhone 5 keyboard glitch is software-related: Fix incoming</title><link>http://www.electricpig.co.uk/2012/10/12/iphone-5-keyboard-glitch-is-software-related-fix-incoming/#comment-679680234</link><description>&lt;p&gt;&lt;/p&gt;&lt;p&gt;I get this issue in other situations too, opening a folder amongst other things causes it. I thought it looks like a faulty graphics chip.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Fri, 12 Oct 2012 07:02:25 -0000</pubDate></item><item><title>Re: Is it live? |  Tenderlovemaking</title><link>http://tenderlovemaking.com/2012/07/30/is-it-live.html#comment-656426843</link><description>&lt;p&gt;I've had a little play with pulling messages off of a redis queue and sending them out to clients (&lt;a href="https://github.com/kernow/rails4-streaming-chat/blob/master/app/controllers/chat_controller.rb)" rel="nofollow noopener" target="_blank" title="https://github.com/kernow/rails4-streaming-chat/blob/master/app/controllers/chat_controller.rb)"&gt;https://github.com/kernow/r...&lt;/a&gt;. My understanding is that each thread handles a single client connection so any message taken from the redis queue it sent out to whichever client's thread happened to process the message. Is there any plans to have some sort of global connection built into ActionController::Live that could send a message to all connected clients or would this be the responsibility of the application to handle this kind of messaging?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Thu, 20 Sep 2012 04:29:46 -0000</pubDate></item><item><title>Re: DailyJS: JavaScript Developer Survey Results</title><link>http://dailyjs.com/2010/12/13/javascript-survey-results/#comment-111231277</link><description>&lt;p&gt;what is it you would like to find out about testing JS? Do you have any experience with it already? I'm thinking about writing a bunch of tutorials on tests so it would be interesting to hear what you want to know about and what level people are at.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Mon, 13 Dec 2010 15:49:26 -0000</pubDate></item><item><title>Re: DailyJS: JavaScript Developer Survey</title><link>http://dailyjs.com/2010/11/29/javascript-survey/#comment-104781300</link><description>&lt;p&gt;ouch, only 32% of people test their JS, explains the huge volume of terrible libraries out there.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Mon, 29 Nov 2010 14:50:22 -0000</pubDate></item><item><title>Re: Bamboo Blog - Taking the Stage</title><link>http://new-bamboo.co.uk/blog/2009/07/27/taking-the-stage#comment-13445508</link><description>&lt;p&gt;Was a good talk, I liked your energetic style. It also made me feel better about the legacy project I'm currently working on. Although I think it could contend with some of your projects for the "worst inherited rails app title" ;)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kernowsoul</dc:creator><pubDate>Tue, 28 Jul 2009 10:16:17 -0000</pubDate></item></channel></rss>