paulbjensen

The trial has been fascinating in its own right for the debate around the principle of freedom of the press vs a person's right to privacy, regardless of everything that has happened since and the other issues surrounding the trial.

Sex tapes seem like a clean cut invasion of privacy, but what if the material in question wasn't a sex tape but a phone call being taped (such as the audio from the tape which revealed that Hogan had made racist comments)? Are the contents of that audio in the public interest?

I think everyone who knows what Gawker are like feel like they played with matches and got their fingers burnt. Whether an invasion of privacy is worthy of a $140m fine is questionable, but it will definitely deter other press organisations from making similar moves to what Gawker did. The implications of that for the press aren't necessarily good, but if the guidance is clear that Sex tape are a no no then I think we can find a sensible middle-ground to the whole issue of the freedom of press and the right to privacy.

MS is nerve damage caused by the nerve cell's coating (Myelin) being mistaken for a foreign body by the immune system, and attacking it. How would the Placebo effect stop and reverse that nerve damage?

Hi, I'm writing a book comparing them both at the moment:

https://www.manning.com/books/cross-platform-desktop-applica...

Having built apps in both, my view is that if you want the tool that fits best with Node.js' conventions, Electron is closer to that philosophy. I say this because of the way that the Node.js contexts of the main (backend) process and the renderer (front-end) process are kept separate. This is different to the way that NW.js has managed to blend the Javascript contexts of both into one, which can lead to odd behaviour when it comes to apps that run with multiple windows.

In terms of momentum, Electron is definitely capturing the most attention and it looks like it will eventually become the goto framework for cross-platform desktop applications over NW.js, which is a shame because NW.js has been around for a while now and was the pioneer of being able to build desktop applications with Node.js.

Team size isn’t the only factor in breaking a monolith into services. In my experience it's been an effective strategy for removing bottlenecks in your application, as well as a way to isolate a piece of code that causes errors and causes the application to crash.

I once worked at AOL (2010-2012). I remember that we were told that we couldn't use AIM for work purposes, and instead were using Yammer and HipChat.

It boggles the mind how a company with a chat product ends up using 2 competing products instead of its own offering.

Let's not forget Grape either: https://github.com/intridea/grape

You could see this move towards JSON APIs way back in 2012 as I suggested here: http://paulbjensen.co.uk/posts/2012/07/11/thoughts-on-rails-....

Some poo-pooed the notion, but you can clearly see that the popularity of realtime frameworks and the way that apps are built client-side heavy is pulling Rails in this direction.

Performance is still the key factor here, and I suspect that's half the reason why you've got some people who espoused Ruby in the past now playing with other languages beginning with Ru, but that have a much less friendly syntax compared to Ruby.

Some welcome changes though nonetheless, especially on the WebSockets front.

True. My notice wasn't accepted until the 2nd version a few days later. Because of that delay, my leaving date moved to the 2nd February, which meant that I received the company's annual bonus payment as I was still on the books in February.

In some ways, you could say that swearing got me my bonus.

I tried to give notice at AOL once. HR rejected the letter due to some expletives, and asked for a revised version. I then submitted a 1-sentence notice.

Lesson learned; don't swear in notices, but also keep it simple. Even if you tried to offer them your honest view of how things were, chances are they'd get filed in a drawer and stuck away.

It took a number of people handing notices day-by-day at AOL before HR clicked that something was wrong, so at that point they invited the Sales team to the NY office (the sales team hadn't been on an overseas trip before). It was a nice gesture of the company; shame that the people got food poisoning on the first night.

Lead Node.js Developer - Starcount, London UK.

Starcount helps businesses to better understand their customers through analysing social media data. It is lead by Clive Humby and Edwina Dunn, the founders of DunnHumby, and the creators of the Tesco ClubCard.

We're looking for a Lead Developer to join us and help us deliver a new audience analytics platform, as well as take our new content curation platform to market.

This is an opportunity to take an important role in a small company during an exciting period of growth and help build a business with the leadership of one of Britain's most successful business couples.

For more details, see the posting here: http://lnug.org/jobs and here: https://careers.stackoverflow.com/jobs/80693/lead-nodejs-dev...

Can't comment on Ruby, but in relation to Node.js in London it's very much a seller's market at the moment; good developers with commercial experience are contracting at £550pd, and very few are interested in taking permanent roles.

It's a good time to be a software developer in London, and not so good if you're trying to recruit one.

As someone who built a dashboard app, I tip my hat: this is a very powerful new feature.

I grew up reading Dune, and then reread it when I was in University. Thanks for sharing this, especially liked how he likened the themes in the book to existing problems of that time.

This is a thoroughly enjoyable game, especially with laser beams and the invisible cloak.

This reminds me of how someone once tried to recruit me with a picture of a giant pair of knockers in a bikini, which had no relation to the job at all. It was kind of insulting.

This article pretty much resonates with my experience, except that my employer (a 4 person established company) can't afford to hire a QA and sysadmin alongside my role as developer.

The bad side is that doing this DevOps role across multiple projects at the same time can lead to burnout, and I think I came close to that in the last few months.

The good side is that I've learnt a great deal about how to architect and deploy distributed web systems, how to do end-to-end testing, and how to effectively run the ops side of the business.

It's a mixed bag, and the burnout is the worst aspect of it, as well as the case where people are forced into situations where they are way in over their head.

In my opinion, the form factor is the key issue.

Ask people if they would wear one? Not just techies, everyday folk out on the street.

Until the form factor is indistinguishable from a pair of sunglasses, this wonderful piece of equipment will remain a niche tool.

I used to work at AOL 2 years ago. It was known within the company that Patch was not going well; even the Huffington Post's localised properties were generating more revenue.

It's easy to say with hindsight that AOL should have tried to let the project grow organically first, with a focus on profitably instead of executing a loss leader strategy, but that seems to be the general consensus here.

It doesn't help either that Patch was being undertaken at a company like AOL. AOL needed to wean itself off of the cash-rich but declining ISP business, and establish itself in the media and advertising industries. Undertaking that challenge at the same time as investing heavily in Patch put the company under a lot of scrutiny.

Thanks to the advertising business doing well, it looks like AOL will be able to run as an independent business, so even though the CEO staked a lot on Patch, I don't think that it will be a fatal blow to his tenure at the company.

It's a shame that he didn't invest that time and money into other promising efforts within the company.

There is this interesting pattern of having template compilation be possible from both the server and the client, such as with AirBnB's Rendr. It gives you the flexibility to choose where you want that template compilation to occur.

With regards to Twitter's Time To First Tweet being slow under their Single Page App, I recall Alex Maccaw mentioning that their JavaScript library execution was inefficient, in that the client had to download a whole bunch of JavaScript before it would load the part of the app responsible for rendering the data.

I believe he was suggesting that if Twitter optimised the delivery so that parts of Twitter's JS were served after the rendering part of Twitter's JS code, then the time to first tweet could be faster.

In my opinion, delegating template compilation to the client offers a nice separation of concerns; the server is the API, and the client is the UI.

It would be interesting if there was benchmarking done into comparing these approaches, to see where server-side template compilation can be beneficial over client-side template compilation.

"There is no worldwide directory of people and, especially, (outdoors) clubs and events and it sucks"

There you go.

I would recommend asking a few outdoors friends whether they feel the same, and see if bringing about this worldwide directory would be a great thing to them.

To me, it sounds like a great opportunity because you have a specific audience to interact with, and there are opportunities to turn it into a business; think of outdoors venues and outdoor equipment companies who would want to promote their products and services to that range of people.

I would recommend asking friends, and in terms of further research, I recommend 2 books: Founders At Work by Jessica Livingston, and The Lean Startup by Eric Ries.

Go for it!

Hi, Thanks.

Working in Finance shouldn't prevent you from working in a startup.

I can recommend trying to scratch your own itch(es) - are there any problems in particular that you run into on a frequent basis, for which existing solutions are poor and you feel could be done in a better way?

Another exercise I could recommend is to ask yourself what would you be doing now, if you were free to work on anything?

Thanks, you're welcome.

I was let go from a social networking startup because I wasn't implementing features as fast as they wanted. At the time it felt like a death sentence on my career as a programmer.

I spent about a week in the doldrums, but then I felt angry, and decided I wasn't going to let their decision define me. I decided to build an app to show what I could do.

I spent 2 1/2 months building an app called Dashku. It was a realtime dashboard, and when I put it on Hacker News, it went to #1 within 45 minutes, and then the server fucked up because the ulimit config on the app server (which I had set but not persisted between reboots) was 1024, and got the flak I deserved for not making sure that the ulimit config has persisted when I configured the machines.

After doing it, these things happened:

- Bechtel contacted me and asked if they could use it internally. They did.

- I had a meeting with Geckoboard. They asked if I wanted to work for them, and I offered to sell Dashku to them. No bite.

- I interviewed at Forward Labs in London. I had about 4 interviews in the space of 2-3 days, but did not get the job offer. I failed to refactor a fill detection algorithm which was functional and fully tested, but memory inefficient. I had stayed up all night to crack it, slept for 2 hours and had no food when I came in for the interview and was asked to refactor it.

ProTip: Sleep well and eat before you go for an interview, otherwise your brain suffers for it.

Eventually, I got a job in London working for webcasting company, and then open sourced Dashku. Here's what happened next:

- Ninja Blocks gave me a free Ninja Block, and asked me if I would like to work with them.

- An Indian health startup asked to integrate Dashku into their IoT robotics app.

- A BI startup basically took Dashku, slapped a coat of paint on it, and called it their own.

- Another IoT startup asked to use it.

- An energy company told me they were going to drop Geckoboard for my app.

- I discovered a professional social network (called Viadeo) had created a wonderful collection of widgets for it.

Then,

- I got an email from someone at Facebook, they said that they were evaluating it for internal use, and asked me if I would like to interview with them in California.

I had to decline as my mother has health problems and I could not move to another country.

All of this, within 14 months of being fired from a startup.

Failure feels like crap, but don't let it define who you are; you have to move on and prove to yourself and to others what you can achieve. I've done that now and found peace with that period in my life.

I should probably thank the guy who fired me.

In the documentary 'Enron: The Smartest Guys in the Room', it mentioned that the company had a "rank-and-yank" system, whereby annually everyone would rank everyone else. Those ranked in the top 10% would be promoted, and those in the bottom 10% would be let go. One guy commented "I don't know a successful company that fires 10% of its employees every year".

You think that's bad, I once worked in a startup where the Product Manager told me he didn't have time for tests.

As a developer watching that video, that line was the one that stood out the most.

There is nothing more frustrating than to be asked to build something using old tools when better options exist, or when you are asked to build apps that don't stretch your abilities, or when you work for people who don't understand how software can change the way that their business operates (who tend to not be technical).

After I graduated from university back in 2006 (studying Management Science), I decided that I liked computers more than I liked Banking or Management Consulting, so I worked for a friend of a friend doing web design, and began to learn Ruby and Ruby on Rails. I read the Pragmatic Programmers books, and spent 6 months at home learning Ruby and Rails in my free time.

About a year later (summer 2007), I got a job working for a ticket search engine called Tickex, doing Rails. I was paid £9 per hour, and worked at a BBQ table and chair. It was a really enjoyable time. we were Seedcamp finalists and nearly got funding from Sequoia, but sadly the funding ran out and the business moved back to California and then shut down. Since then, I've worked at a few other startups, at a web agency called New Bamboo, at AOL, and now I work in a small business. I also had offers to interview at Square and Facebook, but a temporary lack of nationality/family circumstances meant that I couldn't move to California.

The decision to deviate from the path offered by my degree has been one of the best in my life. Before I had learnt to program, I had ideas but no ability to program, so they remained as ideas. Having learnt to program, I have the ability to have ideas and do something about them.

If anyone needs a free dashboard tool for displaying their metrics in realtime, I made this one, which is available on Github: https://github.com/Anephenix/dashku

It's a valuable experience, but can be a very frustrating one to go through, especially if the company has internal power battles and little appreciation for the importance of technology.

It's a very cool idea, I wish I had an excuse to use it.

I've come to the view that CoffeeScript is the marmite of programming languages, and that issues like this will rage on for years to come.

I'd dare and suggest that TJ is JavaScript's DHH; very talented and productive, but also very vocal about he doesn't like.

Programmers are some of the most argumentative people that I know, my father being one of them. When you're immersed in a community, it becomes easy to develop the kind of language bigotry that happens between Rails and Node.js, which is sad and regrettable.

I think that mature programmers see code for what it is and don't get religious or wound up over these things; in the end of the day it's all a bunch of 1s and 0s.