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 FreeBSD Port of Docker
interesting. how does it handle running linux containers? or does this work the same way as boot2docker?
AdrianRossouw··on Recombine to avoid naming when naming is hard
i prefer the varian't that says :

There are only 2 hard problems in programming:

1. naming things.

2. cache invalidation.

3. off by one errors.

AdrianRossouw··on 795 Folsom Ave, Suite 600
seems like it's the address used in twitter bootstrap as an example.
AdrianRossouw··on How Zappos Converts New Hires to Its Bizarre Office Culture
it wouldn't surprise me if a lot of the 200 people who left were from middle management who didn't feel like the new structure provided them with enough ways to advance their careers.
AdrianRossouw··on Fly.js: New generation build system
since i switched to using webpack for bundling, i've pretty much stopped using gulp/grunt completely.

I just found there's very little I needed them for that couldn't be resolved using a makefile or package.json scripts.

I legitimately love gulp though, because it finally let me grok streams.

AdrianRossouw··on Ask HN: My startup has failed. What comes next?
did you end move to budapest?

Last time I spoke to people there, they were only hiring people who were local/willing to move.

AdrianRossouw··on Ask HN: My startup has failed. What comes next?
I highly recommend taking some time for yourself first, just to reconnect to your loved ones and find some kind of stasis in your life. You're going to need the space to rebuild your confidence levels to be able to show the moxie needed to land the right position.

I have found that taking consulting work is a good way to buffer your income for a while, until you find the position that is right for you.

I don't know if e-lance is the correct way to go about it tho, because there is an element of social branding and networking related to all of this.

You could start blogging, or do some presentations at local user groups of various techs. Writing about experiences like what you have been through can actually be very freeing.

AdrianRossouw··on Ask HN: How do you familiarize yourself with a new codebase?
read tests, and then start writing tests for things.

something usually comes up.

AdrianRossouw··on How Adobe keeps key employees from quitting
so they invented 1on1s?
AdrianRossouw··on Ask HN: Do you work with dogmatic, stubborn developers/sysadmins? Are YOU one?
one of the most difficult things to learn when you become more senior is that 'not how i would do it' is a different thing to 'this is broken'.
AdrianRossouw··on Transphobic maintainer should be removed from project – Issue #941
I'm not particularly convinced that "alienating to the community." is really appropriate, because by and large it doesn't seem to be their community up in arms.
AdrianRossouw··on Blackberry might switch to Android as OS
qnx seemed really nifty. I'd been intrigued since the "1.4mb floppy with a full gui" days.

it's a pity they couldn't make it work for them.

AdrianRossouw··on Service-Disoriented Architecture
once again, the question is about how to write a system that can be more easily split into microservices later.

I would separate business logic into a single service and have all other modules call that using a standard protocol like REST or thrift or something.

The issue is that if that logic is being executed all over the system already, it's going to be difficult to break it into a separate service that doesn't do that

AdrianRossouw··on Service-Disoriented Architecture
the question is about building an application that is easier to split into microservices later.

it all comes down to this - http://www.infoq.com/news/2015/01/microservices-sharing-code

If you have multiple components that are depending on the same code, if you try to split them into multiple services that are being independently deployed, you need to keep the code they are depending on in sync.

So making a change to the code shared by multiple services, means you have to deploy multiple services for a single change.

I completely agree with you about the protobuf/thrift angle though. If you're in that situation, you are already doing it right.

AdrianRossouw··on Service-Disoriented Architecture
if you are going to try and separate them out into services later, you need to have the code as compartmentalized as possible.

Otherwise when you eventually split them out, you will end up being in a situation where each service needs copies of all the files it required before.

This then is a situation where you will have to extract into a library, and make general enough to be used and versioned that way.

AdrianRossouw··on Service-Disoriented Architecture
I've seen a couple of codebases now that have coded themselves into corners and made it nearly impossible to go microservices without a major rewrite.

- avoid code sharing wherever possible. It creates an implicit dependency. (If you have a common library or util file, you've done it wrong. try again.)

- don't merge your trees: (ie: each component in the code should have it's own readme and tests folder.)

- write far more unit tests than functional/integration tests.

  (if you separate out components later, those tests can't move with them)
  
- if you use an ORM or similar, you are probably going to have a very bad time about it

  (breaks the no-shared code rule)
AdrianRossouw··on Service-Disoriented Architecture
> In my experience, having small manageable code bases that are responsible for one domain makes things so much easier to develop and maintain.

I think everybody agrees with that.

The issue is that architecting your system like that on a code / repo level means that you gain the complexity of having to manage dependencies between your components, and it complicates the deployment story.

microservices then further complicates things by requiring you to be able to independently deploy each service. this is a lot of complexity to manage for something that doesn't directly solve any problems in your business domain.

This reaction you are seeing is because people have now had enough time to actually work on and hear about projects that were built using microservices. Many of them have found that they don't deliver on their promises, because of the reasons mentioned in the article.

AdrianRossouw··on Ask HN: Why don't websites have 'text only' backup versions?
print stylesheets can be a real pain in the ass to test properly.

at least before chrome web-inspector got the handy checkbox.

AdrianRossouw··on “Nice Ivy League Degree. Now If You Want a Job, Go to Code School”
"bachelor’s degree in psychology and studio art".

The fact that you might need vocational training when trying to get a job that's outside your area of study surprises people ?

AdrianRossouw··on GitHub's down?
the d in github stands for distributed
AdrianRossouw··on Simplify: move code into database functions
I've gone down this road before, and one of my biggest complaints was around managing and deploying the code built this way.

I just found plain server side code easier to reason about.

AdrianRossouw··on Revisiting How We Put Together Linux Systems (2014)
I kinda think that docker changes how a lot of this stuff is put together.

no more shared anything, other than the kernel.

AdrianRossouw··on Talking About Money
for the longest time i was kind of unnerved by how quickly previous employers said yes during negotiation, so I pushed my price up much higher hoping to have a better footing.

so far they've all said yes to what I considered very high.

AdrianRossouw··on The DragonBox Pyra is Nearing Completion
you and me both =)
AdrianRossouw··on Jq – A Command-line JSON processor
i love it so much.

i've used it for things like migrating between json schemas, and even converting normal json into elasticsearch bulk imports on the fly.

AdrianRossouw··on Ask HN: Brag about open-source projects you're proud of
- jsChan [https://github.com/graftjs/jschan]. Our javascript implementation of Docker's libchan library. It implements the same kind of semantics that Go channels have, but over the network, and using node streams. Since it is based on the capabilities of SPDY, it allows you to embed additional channels in messages. So i could request a page, but give you a return channel to write the document to. instead of waiting for the response.

- Graft [https://github.com/graftjs/graft]. Our attempt to determine what microservices taken all the way to the browser would look like. It's a higher level library built on top of jschan. The idea is to be able to use node streams interchangeably on both sides of the pipe, with the communication managed by libchan ... and work invisibly over SPDY or websockets or whatever.

Unfortunately, SPDY was replaced by http2, which meant that libchan went under construction for a bit while the library support was figured out. At the same time, io.js happened. And now there's a very fastly evolving streams spec that is feeding on the whatwg effort to standardise a stream spec for the browser and node.

I am going to take up the mantle again, but there needs to be some settling of the ecosystem first. =\

AdrianRossouw··on Atom Shell is now Electron
i think it's because electron is being used to build more than just atom.

having it be that deeply associated with the other brand reduces the visibility of the project?

AdrianRossouw··on Atom Shell is now Electron
There's a wiki entry for that :

https://github.com/atom/electron/blob/master/docs/developmen...

AdrianRossouw··on Atom Shell is now Electron
interesting to see how many things have already switched to building on electron.

Slack, Mapbox and more.

AdrianRossouw··on Call Me Maybe: MongoDB Stale Reads
Do you have any specific videos we should watch?
← PreviousPage 3 of 19Next →