I have no idea what it's like now, but I went to an open day there years ago and it was incredible. What I learned is there are some extremely ugly Apple varieties that would never get picked up by supermarkets, but tasted unlike anything else I've sampled - literally like candy. Looks like Heritage Fruits still do antique apple tastings periodically: https://www.heritagefruitssociety.org/Antique-Apple-Tastings...
Whenever I've been in seriously challenging situations at work, having real, deep, personal relationships with my team made it far easier to have difficult conversations.
Forging real bonds gives you a foundation that you can actually build a strong team on top of: you can have tough conversations from a position of empathy and compassion; and if you need people to just "get it done", it's much easier to ask a friend to do you a solid and just get the work over the line.
I work for a company with full pay transparency – well, complete transparency across all parts of the organisation – I can't imagine working in an opaque environment ever again. I love it.
My nephew built this as one of his first Mindstorms projects. It works amazingly well, especially given the limited components - quite extraordinary to see in action.
I love this idea. I did a quick pure-CSS implementation, not bullet-proof by any means - biggest downside is it's reliance on the `required` attribute: http://jsfiddle.net/thetron/qpsnH/
I started using Airmail[1], and I love it. Mainly for label support with Gmail, but there's lots of little bits of UI features that I love about. Definitely worth the $1.99 or whatever it is on the App Store.
Thanks for mentioning this! I had completely missed the announcement. That's really exciting, I wonder if pin.net.au will adjust their pricing to match Stripe's. Good to have some healthy competition locally.
With a content-first approach, we develop bespoke digital experiences for some great clients – from global travel and tourism companies to local boutique arts- and media-based clientele – including a long-established interface research relationship with University of Melbourne. We design and develop eCommerce sites, custom CMS-driven sites, Android/iOS apps, digital campaigns and much more. Our clients are Australian, Asia Pacific and UK based, we’re open source and proud, in love with Ruby and all things mobile, and enjoy helping good people futureproof their digital presence. Our flat structure and open communication encourage contribution from every level.
We’re looking for…
An experienced front-end developer to join us in Melbourne, working closely with our design team and technical director. Someone that’s adept at crafting high quality user experiences for desktop and mobile, with at least a couple of years experience in a similar role. A team player, that quickly becomes instrumental in every project, from inception to delivery, as we firmly believe in a collaborative, inclusive approach to our projects.
You’re ideally...
* a lovely person, committed to continual learning and sharing;
* passionate about great web experiences, quality design and fanatical detail;
* experienced in building nice things for appreciative clients and end-users;
* equally happy to contribute to client workshops and design sessions, as you are getting stuck into serious code;
* established and active in the development community, with a GitHub profile we can have a poke at;
We love sentry. We made the switch from Hoptoad/Airbrake, because the pricing based on event volume rather than number of projects. We use it to track a group of small-scale Rails applications - which are growing in number, but reasonably low traffic.
I love everything about it, looking forward to having a poke around the new design!
It's definitely my intention to. At the moment it's a bit of a hodge-podge, but it's definitely on my to-do list to release it as a properly packaged (and tested) rubygem.
We tend to run out of private repos on our organisation gold plan, but have a little ruby script which can pull down some of the older projects (and their wikis), zip them up, archive them to S3 and then remove the repo on Github.
It can also do the reverse, pull the archives down, create a new private repo and push everything back up.
It works quite well, and certainly solved the problem of hitting that ceiling.
You could probably use 'container commands' to start/stop worker processes after each deployment. I'm only reading the Elastic Beanstalk docs for the first time, so I haven't tried it myself - but it looks like it could be the right solution: