There's lots of different types of developers you're going to need to work with over the span of your career in the software business, but the one I want to talk about today is the kind you need when you're trying to build something new.
Finding a developer who can transform a set of ideas into...
The next major milestone for Akka.NET is Akka.NET v1.1, the primary focus of which is a stable, production-ready release of the Akka.Cluster module.
We've made some solid progress towards that goal in some of our maintenance releases, but I came to the realization over the past couple of months that the way we've been working with our contributors isn't the most effective way for the project to achieve these milestones.
In this post I'm going to invite you, a .NET developer who's interested in distributed computing, to work with me directly on the guts of Akka.Cluster and take on a project that's bigger than you or me. And it'll be awesome - you'll learn a...
Last year I had to spend a fair amount of time working on C and C++ projects in Visual Studio 2013, and one of the tasks that I had to learn how to do was use Visual Studio's pre-build and post-build events to copy all of my dependent DLLs into the final output folder for my applications.
In C# we take the ability to do this for granted - if we need to add a reference to another project in our Visual Studio solution we just
Add Reference -->
[Project Name] and boom, we're all set. Visual Studio will automatically copy our dependent binaries into our final
/bin/[Release|Debug] folder automatically.
In C/C++ - hellllllllll no. You have to do this all yourself!
This is an archive of a blog post I wrote for the MarkedUp Analytics blog on July 23rd, 2014. It's been a popular post and I'm posting it here in order to preserve it. I shut down MarkedUp in November, 2014.
The MarkedUp team has had experience developing SDKs, high-performance APIs, working with Cassandra / Hadoop, and service-oriented software for several years. However, when we started laying out the blueprint for MarkedUp In-app Marketing we knew that it would require a radically different set of tools than the traditional stateless HTTP APIs we’d been used to developing for some time.
Picking up where I left off in the previous Helios 2.0 diary entry... After clearing the decks of all of any code I wasn't 100% certain we'd be keeping, I began writing new code.
IChannel, IChannelConfig, and more
Channel interface is chock-full of detailed, helpful comments written by the Netty team and I did my best to port most of those over onto the
IChannel interface in Helios, but I got impatient and left a couple of them to be filled-in as TODOs (send me a PR!)
Next I got to work on porting all of the
ChannelConfig options, which included porting the
The Curiously Recurring Template Pattern
So I noticed something interesting when...
To my eternal shame, I've never blogged about one of the most important open source projects I'm involved in: Helios. Helios is for all intents and purposes a .NET port of Java's wildly successful Netty project, the reactive high-performance socket server that powers the internals of systems like Apache Cassandra and Typesafe's Akka project.
Helios has dutifully powered the remoting layer behind Akka.NET (my main OSS project) for the past couple of years, and is capable of being a powerful tool within the .NET distributed programming ecosystem in its own right.
Helios' job is provide .NET developers with the following tools:
This is an archive of a blog post I wrote for the MarkedUp Analytics blog on February 19th, 2013. It's been a popular post and I'm posting it here in order to preserve it.
When we first made MarkedUp Analytics available on an invite-only basis to back in September we had no idea how quickly the service would be adopted. By the time we completely opened MarkedUp to the public in December, our business was going gangbusters.
But we ran into a massive problem by the end of November: it was clear that RavenDB, our chosen database while we were prototyping our service, wasn’t going to be able to keep growing with us.
So we had to find an alternative database and data analysis system, quickly!
The Nature of Analytic Data
The first place we started was by thinking about our...
Voat exists simulataneously as two different things:
- The Voat software - an open source, ASP.NET MVC + MSSQL implementation of Reddit AND
- voat.co - an instance of the software that is owned and operated by its creators.
I'm a huge fan of Reddit - had an account there for years, and seeing such a kick-ass implementation of it written in C# with SignalR, ASP.NET MVC, Web API, and lots of other cool toys gets me really excited!
Voat could be a huge opportunity to expose lots of curious...
I've done a bit of a "press tour" for Akka.NET since we released Akka.NET v1.0 at the beginning of April and I wanted to share a couple of the interviews I've done in the .NET community since.
I did an interview with Scott Hanselman immediately after .NET Fringe and we covered the goals and scope of the Akka.NET project, but also really took a close look at the Actor model and why it's becoming a popular concept among .NET developers.
Carl and Rich, the two hosts of .NET Rocks, did a better job with the synopsis than I could!
Akka.NET ships! Carl and Richard talk with Aaron Stannard about Akka.NET, a toolkit...
One of central themes of .NET Fringe is open source communities - and there's two sides to this coin:
- How does an open source project successfully attract contributors and make them effective?
- How does your typical software developer become an OSS contributor?
I'm going to touch on the former topic in a subsequent post, as that appeals to a more niche audience than the latter.
Why do open source?
All OSS contributors start...