100% Agree. Only issue is that I'm trying to buy a licence but the payment options seem to be US-only (ZIP code validation). I'm trying to buy from the UK.
853 karma · joined October 26, 2010
I loved how it explained the counter-intuitively of rising crime whilst drug busts put dope on the table, or the risks of an aggressive or non-compliant fishing policy being the EU, or the tale of a group selling their model to a hedge fund for a small fortune.
So many potential ways to use this, and unfortunately I never encountered it at workplaces in my career. I think that’s when you realise that sometimes the ideas have to be presented by yourself.
New Bamboo got acquired by ThoughtBot some years ago.
Scraping the site on a regular basis and taking screenshots is the only way to stop them from scrubbing the reviews.
e.g.
class Admin extends Model {
};
export default Admin;It sounds daft, but I used to repeat a phrase in my head when flying: "safe, calm, happy". It's more of a psychological trick than anything else, but I found it helped me to adjust my thinking at moments.
Recently, I took a role which meant working abroad, and then I realised that I would need to be doing quite a lot of flying to get back for various events. In July I've flown 9 times, 2 of which were on a propeller plane (Bombardier Q400). The experience of doing that many flights means that I don't experience any anxiety when flying, but I still tend to strap myself in a bit more tightly whenever there's some turbulence.
Oh, and the other thing that helps is sitting next in the window seat - being able to look out the window when the plane is taking off, in flight and landing helps. You also get to see some great views.
It's a good watch. RIP Stanislav Petrov.
The company where I work (Starcount) is looking for people to work in data engineering (Hadoop and Spark), frontend (React), backend (Node) and Salesforce admin. If anyone is interested, my email is paul.jensen@starcount.com, and I'm @paulbjensen on Twitter.
- There will be a people drain from Yahoo. Anyone was is passionate about Yahoo will feel completely disenfranchised with being merged into a smaller competitor that is owned by a larger company. Some people will hold out for being made redundant in the hope of a good severance package, and some will simply stay regardless, but those who see what is happening will realise that Yahoo is over, and won't want to be a part of the frankenstein being assembled within Verizon.
- Yahoo's main properties (Homepage, Weather, Finance, Mail) will survive, Flickr/Tumblr I don't know. Tumblr itself has suffered from the difficulties of merging into Yahoo's culture and way of doing things. Flickr was resurrected in some ways, but struggles from the difficulties that other web 2.0 brands have - how to stay relevant and interesting to consumers today when the industry has changed so much since their creation.
- Mayer will go. She tried and she didn't succeed. She'll get a decent severance package, but Tim Armstrong will finally get what he's wanted for a long time. Whether he's able to successfully merge two large-sized businesses together I don't know, this is a different challenge compared to acquiring businesses like Goviral or Millenial Media, we're talking about a headcount of ~8000 employees, and there will be lots of duplicate roles. I don't expect the merger to go smoothly - I expect it to be a bit messy.
Either way, the goal of creating a relatively strong #3 to Google and Facebook seems at this point a lost cause - both Google and Facebook have market valuations that dwarf what AOL and Yahoo were worth at the time of their merger, and given a signal of what we might see in the next couple of years.
Paul
- Writing a book is a huge undertaking - make sure that you have the time to do it.
- Find a good environment to write the book in - if you have kids/pets/others that will interrupt you, try to find somewhere else to do the writing - Marcus Hammerberg (the co-author of Kanban in Action) wrote his in coffee shops, with the side effect that he gained 10lbs, so factor that in.
- Try to pause on blockers if you can - time spent on coding/writing does not always result in the equivalent amount of book being produced.
- Check what the tech landscape for your book's subject is like - if it's very fluid then plan around it - since I started my book, Node.js was forked to create IO.js, Node Webkit was renamed to NW.js, IO.js merged back into Node.js, and then Electron emerged on the scene and now overshadows NW.js (which is ironic given that they have something of a shared history).
- Keep your editor informed - I've had quite an eventful 18 months and it helps to let them know what's going on in your life.
- Writing a book is a great feeling when you see your name as a published author.
I think the one takeaway is that it is like doing a dissertation whilst also doing a job - ask yourself if you can commit to that. If you can, great. And find the right motivation too, because you are putting at least a year of your life into this project.
Would Mozilla ever want to exercise this clause? I don't know - I wonder how they would react if Verizon/AOL ends up buying them, given that Netscape was bought by them early on.
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.
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.
It boggles the mind how a company with a chat product ends up using 2 competing products instead of its own offering.
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.
In some ways, you could say that swearing got me my bonus.
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.