Disqus - Latest Comments for adkron

Re: The best books to start, or improve your Elixir career

Amos King — Wed, 03 Feb 2021 14:52:15 -0000

This is a great list. May I suggest adding Real-Time Phoenix by Stephen Bussey? That is by far my favorite book to showcase the power of Phoenix.

Re: Uploads

Amos King — Mon, 04 Dec 2017 08:44:11 -0000

That was fantastic. Keep it up.

Re: Why is my test failing when I use cast?

Amos King — Fri, 17 Feb 2017 10:43:59 -0000

At the end of your specs that use the cast you can also do a `:sys.get_state(module_name_or_pid)` and that will be a `call`.

Re: [QUESTION] Why Do Scrum Teams Call Agile Iterations “Sprints”?

Amos King — Tue, 21 Oct 2014 11:31:19 -0000

Maybe we need a podcast of continuous flow vs sprints?

Re: [QUESTION] Why Do Scrum Teams Call Agile Iterations “Sprints”?

Amos King — Tue, 21 Oct 2014 11:30:06 -0000

I find that in order to get an accurate sprint estimate that teams need to break down stories as small as they can anyway. When a developer says 3+ days it really means, "I have no idea."

I find that the splitting makes the goal more focused and allows for more prioritization among these micro features. This makes sure that we are actually working on what is the priority and not adding "extra" to the highest feature while failing to get the second highest.

Here are two articles I wrote on story splitting. http://dirtyinformation.com... and http://dirtyinformation.com....

I have had no issues where swarming is difficult because something is broken down too small. In fact I find it simpler if it is broken down. It is simpler to add each person to a different story that way.

Re: [QUESTION] Why Do Scrum Teams Call Agile Iterations “Sprints”?

Amos King — Fri, 17 Oct 2014 11:17:36 -0000

I have not had the same issues with continuous flow and management. The thing about continuous flow is that the focus is at the front pool and if it is emptying. The focus in a scrum sprint is all too often placed at the tail end of the pipe. I've not found a higher complexity with the continuous flow work either. In all the discipline comes on making the stories more coherent and smaller, and less about trying to plan "the right" amount of work. Sometimes you move faster or slower and that is ok. It happens in a sprint too. It is the sprint that is mis-planned that causes the rushed work.

You can still measure velocity in continuous flow. That means planning can still be done, but it changes the focal point of planning to be the beginning of the pipe.

Re: [QUESTION] Why Do Scrum Teams Call Agile Iterations “Sprints”?

Amos King — Thu, 16 Oct 2014 09:53:00 -0000

Ryan, great article. Thanks for the shout out to This Agile Life.

I understand what you are saying, and where the sentiment comes from. I have an issue with the implementation that I see from management and developers. They run, and run, and run, and I think you get the point. There is no rest, and I see the stories completed towards the end of the sprint at a much lower quality. The team begins to focus on getting out the code at all costs. This causes overtime, bad practices, and cutting corners. This is why I prefer continuous flow.

While writing this response I had the thought of calling them "rounds." I think this is a better analogy because the match goes on. It doesn't constitute and end, but it does say we are going to have a resting period. Not many people run a sprint, and then another and another. They do, on the other hand, have multiple rounds in a boxing match. The thought of having the next round might allow developers and managers to still concentrate on quality, and knowing that the fight isn't over. It also constitutes a time of rest. Maybe a day or two between rounds? That day or two should not be a weekend. It should still be coming to work, but reflecting, and getting coaching before jumping into the next round.

Re: http://www.mattsears.com/articles/2011/11/27/ruby-blocks-as-dynamic-callbacks

Amos King — Sun, 01 Dec 2013 21:10:52 -0000

I completely understand that. You had drawn attention to === in the body of the text so I wasn't sure if there was some reason that I wasn't seeing. This is a great idea and I loved reading about your approach. Thanks for sharing.

Re: http://www.mattsears.com/articles/2011/11/27/ruby-blocks-as-dynamic-callbacks

Amos King — Sat, 30 Nov 2013 08:42:59 -0000

I'm not sure I understand why you used === instead of call. I know that === is aliased to call for use cases such as case statements, but I don't really understand what it does for readability here. I'd love to understand why you chose ===.

Re: The Death of Ifs

Amos King — Fri, 02 Aug 2013 21:27:10 -0000

Maybe use a class instance variable? One @ on the class instance variable makes all the difference. Here are the different types of the variable types as an example.

class Foo
@@class_var
@class_instance_var

def initialize
@class_var
end
end

Re: RubyTapas

Amos King — Wed, 05 Jun 2013 19:34:04 -0000

I'm a little behind the times on this, but Struct does not enforce the airity of the constructor.


Point = Struct.new(:x, :y)

Point.new
Point.new(1)
Point.new(1,1)

Each constructor call is valid. It is the same as:


class Point
  def initialize(x = nil, y = nil)
    # ...
  end
end

Re: Continuous integration server from GitLab - GITLAB Blog

Amos King — Wed, 06 Mar 2013 14:13:59 -0000

You can also use vms. Or chroot is a great command for helping with these things.

Re: Continuous integration server from GitLab - GITLAB Blog

Amos King — Wed, 06 Mar 2013 14:12:48 -0000

No actually there are plenty of solutions that handle pulling libraries and dependencies for many languages.

Re: Continuous integration server from GitLab - GITLAB Blog

Amos King — Tue, 26 Feb 2013 11:30:56 -0000

Or you can do the smart thing and use bundler. This is not an issue and was solved years ago.

Re: Rubyconf / Rubygems Hackfest | RubyGems.org

Amos King — Tue, 04 Dec 2012 22:05:36 -0000

I had a great time, and since I've been trying to stay active on the project. I even got most of the people at my local Ruby group setup to hack away. I'm hoping to get some hackathons going on rubygems.

Re: Constrain Yourself

Amos King — Tue, 08 May 2012 13:42:56 -0000

I have moved almost all before filters to constraints. This has allowed for easier testing of controllers, and the controllers can then be moved from app to app. Modularity and allowing the controller to do what it is made for.

Re: http://davidczarnecki.com/post/13636746778

Amos King — Tue, 06 Mar 2012 22:02:09 -0000

I started this in Saint Louis a few months ago. We don't really have regular meetings but it has been great. We just sit around and talk. No formal discussions. Just nice talk about code.

Re: Practicing Ruby - Issue #21: How to practice (1 of 2)

Amos King — Wed, 07 Sep 2011 03:22:48 -0000

This is the first article that really hit home for me. Sometimes I wonder why it is that you are where you are. This article sums it up nicely and gives a great motivator and step forward for many people. We have all heard this same advice, but sometimes a fresh voice can really help.

I've seen you talk a few times, and I could hear you saying that last paragraph. Bravo!

I'd really like to hear about some of your failed attempts too. Sometimes we learn more from failures and knowing that others fail too.

Re: Verifying Propagation of Writes with getLastError - MongoDB

Amos King — Mon, 23 Aug 2010 23:24:42 -0000

"There is an optional wtimeout parameter that allows you to timeout after a certainly number of milliseconds..."
Certainly should be certain.

Re: Ruby Best Practices - Ruby Tuesdays: RBP Chapter 4

Amos King — Sun, 21 Feb 2010 16:55:37 -0000

Remember that the power of Ruby is that a lot of the methods used in file processing can be used in any IO situation. The beginning parser that is discussed could easily be used for parsing input from the console or parsing data coming over TCP/IP. If you are using a *nix based operating system there are a lot of devices that present themselves as files on the system.

Re: Using your mac without the mouse

Amos King — Thu, 04 Feb 2010 13:00:15 -0000

I get invalid file where the video should be.

Re: Ruby Best Practices - Weekend Reading: RBP Chapter 1

Amos King — Fri, 29 Jan 2010 23:27:07 -0000

I did mean to reply to the one above.

Re: Ruby Best Practices - Weekend Reading: RBP Chapter 1

Amos King — Fri, 29 Jan 2010 21:36:55 -0000

Why make any methods private, unless you are using some web framework that maps public methods to urls? They can be a sign of a code smell. Most of the time a private method should be moved to another class or module and be public on that module.

In languages like Ruby private means very little since there are ways to call them any way. They are just a hint to the end user of the api not to use them, but does it hurt to have them exposed? If you give the user of the api access to everything they have a greater chance of using the api in ways you never thought possible. The users are given a greater flexibility.

I'm not saying that just because you have a private method you are doing it wrong. There is a time and place for a private method, but I find very little use for them.

Give the users of your API full access and if they hang themselves with the rope you've given they will learn. Don't document the use of that method and you are good to go. Power users will still find it.

Re: Ruby Best Practices - The Complete Class

Amos King — Wed, 25 Nov 2009 11:29:00 -0000

Thanks, I got it now. I guess most of the time I'm not using objects in that manner. Thanks for the great article. I really enjoyed the read.

Re: Ruby Best Practices - The Complete Class

Amos King — Wed, 25 Nov 2009 10:47:49 -0000

When would you want to dup or clone in an initialize method? I'm looking for something that may break if I don't.