Kommentare für Hendrik Beck http://blog.hendrikbeck.com Tech Startup Craftsmanship Sun, 03 Apr 2016 21:59:00 +0000 hourly 1 http://wordpress.org/?v=3.8.1 Kommentar zu DIY dark-launching feature toggle in 16 lines of Ruby von Fredrik Wendt http://blog.hendrikbeck.com/2015/02/02/ruby-rails-dark-launch-feature-toggle-diy/#comment-75 Sun, 03 Apr 2016 21:59:00 +0000 http://blog.hendrikbeck.com/?p=695#comment-75 Well, I’ve seen code _very_ similar to that work just fine. The biggest challenge I’ve seen with toggles is knowing what you’ve tested, since all those flippers/switches/toggles/gates can be … toggled/switched on/off and typically at runtime. So what code paths did we actually massage in our pipeline(s) – where they relevant to what we’ll have running in production? (Second biggest issue is maintenance and knowing when to remove switches, but that’s highly tied to the context and whether you have control of all production sites or not (not = you deliver to other organisations who in turn develop software based on what you’ve built).)

I think the point of “dark launching” is that whatever you just deployed (let’s call it “next” version), is actually taking on load from real production data (calls, requests, queues, …) so you can observe the “next” version’s behavior without exposing it publicly (so, “in the dark”). (Thus, if the code deployed is not processing production data, I wouldn’t call it a “dark launch”.) This way, you could say that the problem above – “what did we test, and does it say anything about what will run in production?” – is handled by letting the “next” version run along side the “current”, until we’re sufficiently happy that it will work and perform as needed.

Does this makes sense to you?

]]> Kommentar zu Making Continuous Delivery work with Scrum and Sprints von Fredrik Wendt http://blog.hendrikbeck.com/2013/01/14/making-continuous-delivery-work-with-scrum-and-sprints/#comment-74 Sun, 03 Apr 2016 21:41:00 +0000 http://blog.hendrikbeck.com/?p=344#comment-74 +1!
What’s the point of talking about what’s been done at the sprint review, in your mind? (I may be stuck on the words “do/been done”, as that’s not so interesting from a product point of view. What we’ve learned, and what attributes/features the product contains (and how they perform/impact users) should be more relevant than “this is work we have done”. But I’m guessing you’re also way passed that?)

]]> Kommentar zu Making Continuous Delivery work with Scrum and Sprints von hendrikbeck http://blog.hendrikbeck.com/2013/01/14/making-continuous-delivery-work-with-scrum-and-sprints/#comment-73 Sun, 03 Apr 2016 21:24:00 +0000 http://blog.hendrikbeck.com/?p=344#comment-73 A few additional words: I have come to value immediate or near-immediate releases of small features (hence reducing the amount of unreleased code) and immediate customer feedback *a lot*. The sprint review is more of a regular internal checkpoint of the team (and its stakeholders) to look at what’s been done and what that means going forward (e.g. re-prioritizing the backlog etc.). No need whatsoever in my eyes to wait for the sprint review before releasing features.

]]> Kommentar zu DIY dark-launching feature toggle in 16 lines of Ruby von hendrikbeck http://blog.hendrikbeck.com/2015/02/02/ruby-rails-dark-launch-feature-toggle-diy/#comment-72 Sun, 03 Apr 2016 21:16:00 +0000 http://blog.hendrikbeck.com/?p=695#comment-72 Hey Fredrik,

thanks for your comment.

I don’t actually want to try too hard to defend what I did here, wasn’t really my finest hour and more of a little hack than anything serious.

But since for the sake of the argument: I would say you could use the toggle to limit access to new features on different levels. For example, the pieces of code that receive calls can be open and let load onto the system while at the same time limiting certain UI features that give users access to the new data. In that case it would satisfy your definition of dark launching, wouldn’t it?

So, my point is that it’s rather up to how you use it whether it’s dark launching or just toggling a few lines of code. What do you think?

Cheers
Hendrik

]]> Kommentar zu DIY dark-launching feature toggle in 16 lines of Ruby von Fredrik Wendt http://blog.hendrikbeck.com/2015/02/02/ruby-rails-dark-launch-feature-toggle-diy/#comment-71 Sun, 03 Apr 2016 19:59:00 +0000 http://blog.hendrikbeck.com/?p=695#comment-71 Hi Hendrik!
I wouldn’t call this Dark launching, as the new code is not exercised. I would call this simply (binary) a feature toggle. For it to be a Dark launch, I expect the new system or code to receive calls, so that you can observe whether the “dark” system/code will handle the load it will receive once public, and the correctness of the results it produces. These results, however, aren’t made public. Hence the system operates in the “dark”, in the shadows of the real system that the public can see.

]]> Kommentar zu Making Continuous Delivery work with Scrum and Sprints von Fredrik Wendt http://blog.hendrikbeck.com/2013/01/14/making-continuous-delivery-work-with-scrum-and-sprints/#comment-70 Sun, 03 Apr 2016 19:52:00 +0000 http://blog.hendrikbeck.com/?p=344#comment-70 I completely disagree! The point of the Sprint Review is to inspect a product increment – ie the product – _as it is right now, with only Done functionality (new and existing)_ in relationship to the market (which is why stakeholders are there), so that we can adapt the product backlog to maximize the (potential) value of future work. “Future work” may include “release to market” if we haven’t done so yet. It may be “roll out to everyone” if a feature is currently in production, but turned on only for a subset of users.

]]> Kommentar zu Where are the Java User Groups in Vietnam and in South-East Asia? von Adam Skelton http://blog.hendrikbeck.com/2013/03/30/where-are-the-java-user-groups-in-vietnam-and-in-south-east-asia/#comment-69 Mon, 01 Feb 2016 01:41:00 +0000 http://blog.hendrikbeck.com/?p=405#comment-69 Hi Hendrik, I’m wondering if there is any news about local user groups? Did you manage to find any?

]]> Kommentar zu Making Continuous Delivery work with Scrum and Sprints von thisGuy http://blog.hendrikbeck.com/2013/01/14/making-continuous-delivery-work-with-scrum-and-sprints/#comment-68 Tue, 17 Nov 2015 23:17:00 +0000 http://blog.hendrikbeck.com/?p=344#comment-68 sprint reviews are not supposed to be of items in production..

]]> Kommentar zu Where are the Java User Groups in Vietnam and in South-East Asia? von Adam Skelton http://blog.hendrikbeck.com/2013/03/30/where-are-the-java-user-groups-in-vietnam-and-in-south-east-asia/#comment-67 Thu, 09 Jul 2015 11:53:00 +0000 http://blog.hendrikbeck.com/?p=405#comment-67 Many thanks for your help Hendrik, it’s much appreciated. We are looking to gain exposure for our software products in this region and if you do happen to know from your experience there any local websites/events/communities that revolve around .NET or Java I would love to know.

]]> Kommentar zu Where are the Java User Groups in Vietnam and in South-East Asia? von hendrikbeck http://blog.hendrikbeck.com/2013/03/30/where-are-the-java-user-groups-in-vietnam-and-in-south-east-asia/#comment-66 Thu, 09 Jul 2015 10:14:00 +0000 http://blog.hendrikbeck.com/?p=405#comment-66 Interesting. I lived there for a few years, doing software development. If there’s anything I can help you with, I’d love to do so. If you’ve got specific questions, feel free to DM me and ask them. Or if you’re looking for particular groups or skill sets or anything like that, I’d be happy to try as well. I mostly lived in Vietnam, so that’s what it would be most likely that I could help with. The offer stands :-)

]]>