Los Techies - Latest Comments

Re: RabbitMQ for Windows: Fanout Exchanges

Mike Hadlow — Wed, 16 May 2012 10:18:23 -0000

Great series Derek. Can I make a shameless plug for my simplified and opinionated RabbitMQ API for .NET, EasyNetQ ;)

https://github.com/mikehadlow/...

Re: JavaScript Closures Explained

Alan K Fadliawan — Sat, 12 May 2012 11:01:52 -0000

Good job. The diagrams are easily understood and I like how you use the term 'pairing'. Thanks!

Re: RabbitMQ for Windows: Introduction

Bryan Nehl — Sun, 15 Apr 2012 23:47:23 -0000

Thanks for this post. I was trying to get the management console working with no luck and came across this post. They key thing I was missing was to run from an elevated command prompt. Did that and got the server working! Without that, everything looked like it was working and installed but the web server wasn't up. Thanks. :)

Re: RabbitMQ for Windows: Introduction

Fernando Zamora Jimenez — Mon, 19 Mar 2012 01:13:54 -0000

In other words the receiver may be down but it can pickup the messages once it comes backup since they are in a queue. I'm not sure if the "asynchronous workflow" covers this already.

Re: RabbitMQ for Windows: Introduction

Fernando Zamora Jimenez — Mon, 19 Mar 2012 01:12:20 -0000

hmmm... I always thought one of the big reasons for message queueing service was because both systems sender and receiver are not necessarily connected at the same time. This would allow the receiver and sender to send and receive on independent schedules from one another.

Re: RabbitMQ for Windows: Introduction

Fernando Zamora Jimenez — Mon, 19 Mar 2012 01:09:18 -0000

Thanks for sharing. Can't wait for your next post. You kinda left me hanging! Just Kidding. Thanks again for sharing.

Re: RabbitMQ for Windows: Introduction

derekgreer — Sat, 10 Mar 2012 12:05:31 -0000

Hey, Joe. Most situations where you have a point-to-point connection (e.g. client/server, RPC, Web Services, etc.) can be facilitated by messaging and often with more ease, so you might consider it for that reason alone.

Some situations where you should consider using messaging are:

- When you have a heterogeneous development environment
- When you have asynchronous workflow needs
- When you need to monitor communication
- When you have high reliability needs
- When you need scalability
- When you hate XML

Re: Dependency Management in .Net: Offline Dependencies with NuGet Command Line Tool

NA — Fri, 09 Mar 2012 19:31:19 -0000

Interesting read. Thanks for posting!

Re: RabbitMQ for Windows: Introduction

Joe — Tue, 06 Mar 2012 13:05:56 -0000

Derek,

Can you cover when and why you'd use a a message queue solution (be it RabbitMQ or any other)?

Re: JavaScript Closures Explained

Shahar Shelly — Wed, 22 Feb 2012 03:15:33 -0000

Great Post .
Thanks.

Re: JavaScript Closures Explained

Tal Ater — Tue, 21 Feb 2012 02:38:08 -0000

Great post! I really enjoyed this one.

Re: JavaScript Closures Explained

Andrew Turner — Sat, 18 Feb 2012 16:04:40 -0000

I just purchased your book for my mobile devices. Thanks for bringing it up. I have also blogged, tweeted, and posted info about it.

Re: JavaScript Closures Explained

Andrew Turner — Sat, 18 Feb 2012 16:01:17 -0000

Thank you for explaining the technical aspects in detail. Your use of diagrams is particularly helpful. I have added your rss feed to my google reader collection, and look forward to reading your subsequent posts!

Re: JavaScript Closures Explained

mjy — Sat, 18 Feb 2012 11:34:23 -0000

Good job! I found closures one of the most difficult JavaScript features to explain in my book "JavaScript: Just the Basics - A Primer for the Complete Beginner." Thanks.

Re: JavaScript Closures Explained

David Fox — Fri, 17 Feb 2012 16:50:26 -0000

Thanks! Even as a JavaScript amateur, this was very informative. I've been using closures without knowing it.

Re: Effective Tests: A Test-First Example – Part 1

Leon van Bokhorst — Sat, 11 Feb 2012 04:33:04 -0000

Great series!

Re: Effective Tests: Double Strategies

Tomek Kaczanowski — Tue, 17 Jan 2012 16:49:35 -0000

I have to say that this blog post goes beyond language difference and applies also to Java. I liked the most recommendation number 4 "Focus on Behavior". Thank you, that was really interesting.

Re: How To Produce Bug-Free Software

kevdog — Tue, 18 Oct 2011 14:06:37 -0000

Very smart post. Thanks for this.

Re: How To Produce Bug-Free Software

Enrique — Tue, 18 Oct 2011 07:49:55 -0000

Over twenty years ago I heard Tom Gilb explain the difference between a bug and a defect. What you have tried to redefine as a bug is close to what he defines as a defect. I also believe Tom Gilb's definition of the term defect is essentially an industry standard, at least for those who are in the know about such things.

Re: How To Produce Bug-Free Software

alberto rodriguez — Tue, 18 Oct 2011 02:56:30 -0000

So, in order to demonstrate it's possible to produce bug-free code, let's start by redefining what a bug is... I see what you did here. clever! :P

Re: Dependency Management in .Net: install2

derekgreer — Wed, 05 Oct 2011 14:44:08 -0000

The intent of this extension is to use it as part of your CI build process, so I don't see OpenWrap or NuGet Powertools presenting any advantages over this from a CI perspective. This solution does have its own advantages, however, in that it isn't tied to any particular build tool (OpenWrap and NuGet Powertools both rely upon custom MSBuild tasks and modification of your project files to work) and it allows you to maintain a simple solution-wide manifest to denote your project's dependencies.

Re: Dependency Management in .Net: install2

Chris Pont — Wed, 05 Oct 2011 12:12:40 -0000

Good work, and a nice simple solution.

Similar to OpenWrap, but NuGet Powertools does this too, as described here... http://bit.ly/n79hA0
The advantage is that if you build using CI such as Jenkins, the dependencies will be resolved every time, and NuGet will keep the configs up to date if you decide to upgrade any packages.

Re: Dependency Management in .Net: install2

Todd Edwin King — Wed, 28 Sep 2011 14:14:05 -0000

Project file modification notwithstanding, we use MSBuild and find that convenient. I'm sure OpenWrap's goal is to have no specific build tool dependency.

As to "magical" referencing of assemblies, that is what enables the system we have built to manage cross-team dependencies. Dependencies are not kept with source code (except where necessary) and are pulled during build process.

This goes well beyond NuGet and OpenWrap purview, but our needs go well beyond just making it easy to get and maintain open source dependencies.

Cheers

Re: Dependency Management in .Net: install2

derekgreer — Wed, 28 Sep 2011 11:12:04 -0000

The advantage of this approach is that it provides solution-level dependency management independent of any particular build tool. One of the things I don't like about OpenWrap is the modification of project files to insert hooks to OpenWrap's custom MSBuild tasks. I'm also not sure I like the "magical" referencing of all assemblies.

Re: Dependency Management in .Net: install2

Todd Edwin King — Wed, 28 Sep 2011 10:39:57 -0000

OpenWrap solves this problem pretty well now, and I hope better in the next version(s). These build time objectives are what led me to OpenWrap after I determined that NuGet's scope/objectives aren't as powerful/useful as I was hoping.

It's good to see extensions like this though, as it looks like there is hunger for more advanced usages of NuGet.