Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
AdrianRossouw
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
15 ms
·
61.
▲
by
AdrianRossouw
11y ago
This is a nice client-side markdown editor for gh-pages : http://prose.io/
62.
▲
Professor Frisby's Mostly Adequate Guide to Functional Programming (2015)
(mostly-adequate.gitbooks.io)
3 points
by
AdrianRossouw
11y ago
|
0 comments
63.
▲
by
AdrianRossouw
11y ago
perfect social engineering.
64.
▲
by
AdrianRossouw
11y ago
it's the only app I've ever used where I don't end up fighting to make the splines do what I want them to. It's truly a gem.
65.
▲
by
AdrianRossouw
11y ago
I found that switching to consulting, and charging a day rate is the first time that it finally clicked for me that I need to stop after 8 hours. by working longer hours, i was reducing the value of my time. I was also reducing the value
66.
▲
by
AdrianRossouw
11y ago
interesting. how does it handle running linux containers? or does this work the same way as boot2docker?
67.
▲
by
AdrianRossouw
11y ago
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.
68.
▲
by
AdrianRossouw
11y ago
seems like it's the address used in twitter bootstrap as an example.
69.
▲
by
AdrianRossouw
11y ago
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.
70.
▲
by
AdrianRossouw
11y ago
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.
71.
▲
by
AdrianRossouw
11y ago
did you end move to budapest? Last time I spoke to people there, they were only hiring people who were local/willing to move.
72.
▲
by
AdrianRossouw
11y ago
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 neede
73.
▲
by
AdrianRossouw
11y ago
read tests, and then start writing tests for things. something usually comes up.
74.
▲
by
AdrianRossouw
11y ago
so they invented 1on1s?
75.
▲
by
AdrianRossouw
11y ago
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'.
76.
▲
by
AdrianRossouw
11y ago
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.
77.
▲
by
AdrianRossouw
11y ago
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.
78.
▲
by
AdrianRossouw
11y ago
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 o
79.
▲
by
AdrianRossouw
11y ago
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 co
80.
▲
by
AdrianRossouw
11y ago
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 copie
81.
▲
by
AdrianRossouw
11y ago
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 y
82.
▲
by
AdrianRossouw
11y ago
> 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
83.
▲
by
AdrianRossouw
11y ago
print stylesheets can be a real pain in the ass to test properly. at least before chrome web-inspector got the handy checkbox.
84.
▲
by
AdrianRossouw
11y ago
"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 ?
85.
▲
by
AdrianRossouw
11y ago
the d in github stands for distributed
86.
▲
by
AdrianRossouw
11y ago
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.
87.
▲
by
AdrianRossouw
11y ago
I kinda think that docker changes how a lot of this stuff is put together. no more shared anything, other than the kernel.
88.
▲
by
AdrianRossouw
11y ago
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.
89.
▲
by
AdrianRossouw
11y ago
you and me both =)
90.
▲
by
AdrianRossouw
11y ago
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.
More ›