HNHacker News
TopNewBestAskShowJobs

AdrianRossouw

1,265 karma · joined December 6, 2011

[ my public key: https://keybase.io/adrianrossouw; my proof: https://keybase.io/adrianrossouw/sigs/qeiKCiA_nJFzkyUgeideVT3Dpcspt7_NrH9mvbUrMwY ]
submissionscomments
AdrianRossouw··on Open Sourcing super expensive proprietary software
i don't think SOA invented a problem at all. I think the problem existed, and has existed, for as long as we have been building distributed systems.

SOA over-engineered though, and basically strangled any practical use it had by having layers upon layers of enterprise blah built on top of it.

microservices is the new wave of the 'well, we have this problem' that is springing up.

it says you need a lightweight communication layer (basically REST by default), and then you use whatever transport suits the problem.

Full-stack is basically meaningless by the way. It really depends on how big your "stack" is, and once you take a far enough step back, the web front-end is such a tiny part of the problem space.

http://wayfinder.co/pathways/535e46a318fbce1100cf7f2a/the-va...

AdrianRossouw··on Open Sourcing super expensive proprietary software
> yes a machine readable data format, but NOT XML and yes, JSON is likely/probably good enough

I thought so too, until I realized json is terrible for binary. on it's own it can't reproduce the full capabilities of REST ie: http multi-part uploads.

You need a performant streamable binary format too, and my vote for that is protobuf.

AdrianRossouw··on Open Sourcing super expensive proprietary software
> I see a clear decline of SOA and a push towards open source

everything old is new again.

http://wayfinder.co/pathways/53536427f7040a11002ae407/a-fiel...

AdrianRossouw··on We Are All Wrong About Software Design
straw man if I ever saw one.

not liking an orm doesn't mean putting sql in a template is acceptable.

AdrianRossouw··on Ask HN: Did you have a mentor? Have you ever mentored someone?
So i've been doing a lot of mentoring, especially recently.

A large part of it was due to my involvement in open source for over a decade, because being an ambassador for a project involves helping new people get started.

I do it partly because I love the way people's eyes light up when something finally clicks, and they see the possibilities. It don't even have to be physically there to enjoy that.

The last while it's become obvious that I need to expand how many people I am helping. So i've started writing things down in my blog, to guide people through what "Full Stack" development entails.

I just posted my second post in the series here:

https://news.ycombinator.com/item?id=7657585

Feel free to ping me, although I don't really do the 1-to-1 thing. I sometimes pass my drafts through multiple sets of eyes to refine the message I need to spread.

You can find my contact details on my online portfolio.

AdrianRossouw··on What does "Full-Stack" mean?
This is the second part in my series on full-stack fundamentals.

I tried to narrow down what "full-stack engineer" actually meant, and I discovered it was largely meaningless due to the fact that "stack" isn't really defined. part 1:

http://daemon.co.za/2014/04/introduction-fullstack-fundament...

Here's an outline of the rest of the series planned so far:

http://imgur.com/qsGqFFk

Feel free to ask any questions/make any suggestions here.

I will be following up with a curated set of references in the same format as this post:

http://wayfinder.co/pathways/53536427f7040a11002ae407/a-fiel...

I've also taken over http://reddit.com/r/fullstack to host discussions on this, and any other future topics I cover.

AdrianRossouw··on Why You Shouldn't Say It's Easy When Teaching
Easy and Hard are relative terms.

Simple and Complex are objective terms.

Rich Hickey explains it very well in the presentation "Simple Made Easy", that I have some notes on here.

http://daemon.co.za/2014/03/simple-and-easy-vocabulary-to-de...

AdrianRossouw··on Famo.us So Far: Field Guide for April 2014
Let's clear up some misconceptions quickly:

1. I think they botched their 'launch', badly. 2. It is completely open source: repo[1] , examples[2] , docs[3] 3. It's not magic either: this is why it's fast[4] 4. What is in the beta is access to the demos and tutorials, which take the form of something like codecademy.

A picture says a thousand words, so let's try this. screenshot from positioning page of interactive tutorial[5] .

---

[1] https://github.com/Famous

[2] https://github.com/Famous/examples/tree/master/src/examples

[3] http://famo.us/guides/

[4] http://www.html5rocks.com/en/tutorials/speed/high-performanc...

[5] http://i.imgur.com/08gn1sf.png

---

It gives you the absolutely pain free way to center any surface (which is just a DOM element) both vertically and horizontally.

    { origin: [0, 0] } // left top corner
    { origin: [1, 1] } // bottom right corner
    { origin: [0.5, 0.5] } // dead center

    // and THEN....

    { size: [500, undefined] } // full height column sidebar
    { size: [undefined, 100] } // full width footer
    { size: [undefined, undefined] } // full screen surface
    
    
I think this is a breath of fresh air, and I'm going to build more stuff with it (or something that is like it), because I really think it makes the code much much easier to reason about.

This is how you make responsive layouts in it[6]. If size > width. so much simpler than media queries and css overrides and what not.

---

[6] http://stackoverflow.com/questions/23140046/what-is-the-best...

---

What they have done is package known good techniques in a way that I would actually consider using them in real projects with mid level developers who might not otherwise understand the nuances of linear algebra. I sure as hell don't, but this makes it accessible.

I am honestly not affiliated. I knew it existed, but I recently discovered a good reason to play with it, so i figured it out from the examples and the docs.

While compiling this, I was unable to find any dissenting opinions from anyone who actually had tried it, because of how the launch went down. I think more people should try it before they reject it.

Just play with it. Please.

AdrianRossouw··on Ask HN: Software developers with good media presence?
ask open source developers you admire? or just find blogs that you like with related topics.
AdrianRossouw··on A New Codecademy
thanks man!

bookmarked.

AdrianRossouw··on A New Codecademy
I'm feeling like a bit of a spammer posting about this so often, but I think it's just coming up so often because it's a real need.

I've started writing a series of posts about the fundamentals of full-stack development. It came out of what I have been explaining some students I have been mentoring recently.

http://daemon.co.za/2014/04/introduction-fullstack-fundament...

My goal is to explain the different layers, the concepts at play in them, and how they interact with each other.

"It's a roadmap, not a recipe book". The format is going to end up being similar to this post about microservices I built.

http://wayfinder.co/pathways/53536427f7040a11002ae407/a-fiel...

This is the outline so far : http://i.imgur.com/qsGqFFk.png

AdrianRossouw··on How to be a great software developer
Or you can just acknowledge that we are limited. all of us.

Once you realize that, aiming for simplicity first is the obvious choice.

http://en.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_...

AdrianRossouw··on How to be a great software developer
I agree with most of his points, and the parts we disagree on are more of a philosophical difference.

I'm more of a sinatra-type than a rails-type, and I don't really trust 'frameworks' that try to do so many things for so many people. I like my dependencies to have a much more clearly defined scope with fewer assumptions made.

I also don't think loc is an indicator of simplicity. Removing duplication as in his example, sure. But it being one line of code versus being 10 lines of code because it relies on a specific set of side effects, that may drift over time... not so much.

AdrianRossouw··on How to be a great software developer
> You should aim for simplicity and over the years I have learned that simplicity is far more easily attained by time spent working and refactoring than hours of pure thought and “brilliance”.

Yup. It was Rich Hickey's presentation "Simple Made Easy" that finally allowed me to put it into words. I got so frustrated about only having a 1 hour presentation to link people to, that I ended up writing some notes to be able to refer people to.

This is the money shot I think.

http://daemon.co.za/2014/03/how-complexity-affects-software/

This is also really relevant:

http://thecodelesscode.com/case/108

AdrianRossouw··on Code as if everyone is the thief.
flagging this because it's blogspam - original: http://thecodelesscode.com/case/140

i know etiquette says not to post a comment, but the reason did need to be communicated somehow.

AdrianRossouw··on The Philosophy of Computer Science
I was looking for articles to reference around the nature of logic in philosophy and programming, but this is far more interesting I think..

This contains various different ways of thinking about computer science, such as the nature of computation or abstraction.

AdrianRossouw··on What should a self-taught programmer study?
Rich Hickey's presentation "Simple Made Easy" changed how I communicate about software complexity.

I got so frustrated about only having a 1 hour presentation to link people to, that I ended up writing some notes to be able to refer to them later.

http://daemon.co.za/2014/03/simple-and-easy-vocabulary-to-de...

AdrianRossouw··on What should a self-taught programmer study?
I just started a series of blog posts that handle some of the more complex subjects in a clear and relatable manner.

http://daemon.co.za/2014/04/introduction-fullstack-fundament...

This is a roadmap, not a recipe book. I want to give people a bit of surface area to grab onto when learning these things, so they can figure out how all the pieces relate to each other.

here's a trello of the planned posts so far (several outlines/drafts already): http://i.imgur.com/txu4yd3.png

Any ideas about what I should write about would also be useful.

AdrianRossouw··on Introducing jsfmt
wow. that blog post was really hard to parse because it buried the lead so deep.

from the github repo

jsfmt formats javascript and allows AST searching and rewriting

AdrianRossouw··on Computer Science from the Bottom Up
The simple english wikipedia has some useful entries on this kind of thing actually.
AdrianRossouw··on Computer Science from the Bottom Up
man, i really wish this went deeper into data structures and their nature, instead of just diving into binary math and c memory management specifics.

I'm not going to get as much use from this as I thought at first glance =/

does anybody know of any other good references to point people to when discussing the basics?

AdrianRossouw··on Computer Science from the Bottom Up
This is a really useful resource.

I've started to do something quite similar on my blog. I've been mentoring some web developers who only know html+css, and i've been using the time to write about the whole stack.

My goal is to build a roadmap, not to write a recipe book.

I've just started, but this is going to be a very useful reference for when I need to explain some of the more complex ideas.

http://daemon.co.za/2014/04/introduction-fullstack-fundament...

AdrianRossouw··on Building an English Auction With MongoDB
just so we're clear. I did read the article, but not the linked paper.

> I spent a fair amount of time visiting engineering teams that have built internet auctions, most of which were transactional systems where taking a position on an item involved starting a transaction, running an auction round and committing the changes.

That sounds pretty straight forward, where are the pain points?

>In contrast, we chose to deliver a simpler, eventually consistent system on top of MongoDB, in which all data is immutable and where some level of serialization occurs within a single background process.

why was that simpler? what was stopping you from just inserting records instead of updating them? and why did it matter that serialization occurs in a single background process?

AdrianRossouw··on Building an English Auction With MongoDB
So why would SQL not have been a good enough solution to this?

Not trolling, I'm genuinely asking.

I've been trying to gather objective information from people who have actually been successful with mongo about exactly why mongo was the best tool for that job.

http://daemon.co.za/2014/04/when-is-mongodb-the-right-tool

AdrianRossouw··on Programmers' Proverbs (I'd love some input)
Show me you algorithm and I will remain puzzled, but show me your data structure and I will be enlightened.

-- Old programming proverb

You should totally read codelesscode too - http://thecodelesscode.com/

AdrianRossouw··on Why The Clock is Ticking for MongoDB
Well, I was imagining a situation where you had multiple different pieces in a game, relating to each player and distinct to that game. Maybe like an RTS game or something?

So you might want to query how many pieces a certain player has available, or do a check on who this piece belongs to.

Keep in mind I'm still not saying an actual game, but any problem that had similar data storage and access patterns as a game along these lines would have.

I don't know enough about firebase to confirm whether it is suited to this, but if I had any kind of backend at all, and I had requirements for really quick reponses, i wouldn't be comfortable adding the extra hop to a hosted service onto each call.

AdrianRossouw··on Why The Clock is Ticking for MongoDB
I've been asking a lot of people when MongoDB is actually the right tool for the job.

http://daemon.co.za/2014/04/when-is-mongodb-the-right-tool

I'm starting to form this idea of what constitutes an ideal use case for mongo in my head, and i'm trying to prove the model.

If I were to imagine some kind of "realtime" multiplayer game, like quake or something.

1. You have to have the state be shared between all the parties in a reasonable time.

2. The clients only need the data that is directly relating to the round they are in, so you have the concept of cold and hot data.

3. The data is all kind of ephemeral too, so that you don't specifically care about who was on what bouncy pad when, but you do want to know what the kill score/ratio is afterwards.

4. You have a couple of entities that have some kind of lightweight relationship to each other, which makes it just more complex than a key-value store like redis is really suitable for.

5. These entities are sort of a shared state, and thus get updated more often than new unrelated documents get added, and couchdb's ref-counting and append-only nature makes it really unsuited for constant updates of an existing record.

any feedback would be appreciated.

AdrianRossouw··on Ask HN: If you worked with a grad from a code bootcamp, how effective were they?
they are still a tiny bit too exclusive to become this generation's MCSE, but they are getting there.
AdrianRossouw··on Fear of Macros
I don't know what they authored the documentation, but I quite like what gitbook.io is doing in this space.
AdrianRossouw··on Ask HN: If you worked with a grad from a code bootcamp, how effective were they?
I've noticed the same need, which is why I started a series of articles trying to cover that stuff.

http://daemon.co.za/2014/04/introduction-fullstack-fundament...

← PreviousPage 6 of 19Next →