eccp

Not sure what you mean with "Netflix not working natively" but on Linux you just need either Chromium or a recent version of Firefox (maybe not the ERS version) and enable it to play DRM content. It just works.

- anime/subs related stuff

- webcomics (xkcd, alberto montt)

- music (boards of canada wiki, music for programming.net)

- java stuff (adam bien, onjava.com, planet clojure, grails.io, the server side, the cognicast)

- job boards (wfh.io, functional jobs, stack overflow careers, clojurework.com)

- coding stuff (atomic spin, adam bard, ycombinator, /r/clojure, the changelog, infoq)

- mixed bag (ars technica, some reddits, waxy.org, thisiscolosal.com, etc.)

I used FreshBooks.com when I freelanced a few years ago and I think it contained all the features you want and it was pretty inexpensive (~10 USD per month) and invoices/receipts looked very professional and allows setting different currencies for each client (eg. if you work remotely for different international clients).

I've been reading bits about Erlang and Lisp-flavored Erlang (http://lfe.io/). I ported Norvig's Lispy (http://norvig.com/lispy.html) to Java as a weekend project and now I'm curious about Pixie (https://github.com/pixie-lang/pixie)

I follow all of them via RSS. In English: Hacker News, InfoQ, Planet Clojure, O'Reilly Radar (and ocasionally listen their podcast in SoundCloud), Ars Technica, The Server Side. I save some episodes of some podcasts which I find interesting (eg. The Cognicast) but takes me a long time to catch up.

I also follow some tech blogs in Spanish: Microsiervos, Fayerwayer, Manzana Mecanica, Hipertextual, Genciencia.

This was my favourite App from the Clojure Cup 2014, had so many laughs by adding every repo I had to unlock new achievements.

Also, if you don't have the OS or the hardware to run some of the most recent, interesting demos, you can watch them via this YouTube channel: http://youtube.com/user/annikras

This. Don't wait until everything is perfect. If your side project does a barely minimum to be usable, just release it somewhere (if it's an open source project) or deploy it and send a message for other people to try it.

Other people's feedback is a huge factor in being motivated.

Not a specific language, but you should try learning about functional programming (eg. Java 8, Clojure, Scala, Haskell).

Also, if you want a brief overview of different paradigms you should check "Seven Languages in Seven Weeks" (https://pragprog.com/book/btlang/seven-languages-in-seven-we...)

I was on a remote position for several years, maintaining code written by several other developers over the course of 10 years, poorly written and no spec in sight. I sincerely tried to move it forward to current standards, one bit at a time. It improved a bit for a while but from the distance it was a mess and I doubt some of the improvements will ever get deployed.

I went to a lot of stress during that period, but on the other hand it felt comfortable, sharing only a few hours of the day to touchbase gave me freedom to organize the time with the family, there were not many challenges other than managing a big ball of mud, and the hourly rate was much better than my colleagues did working on-site.

On the other hand, there was no prospect of new challenges, or technologies or salary, this was a small business. I did some side projects recently and it gave me confidence to move forward: there were many other companies willing to work remotely with newer technologies and with a better rate.

The show is still on air in Chile in one of the largest TV channels. I'm in my late 30s and I remember the show was rather old already when I was a kid :-)

Now seeing the show with the eyes of an adult feels like a portrait of a much simpler but much poorer era. El Chavo (mexican slang for "the kid") was a boy who slept inside a barrel in the shared patio of a slum ("la vecindad") where most of the action happens. With plenty of physical humor, El Chavo was frequently hit in the head as a punishment in the show, specially by Don Ramón, a character which would never find a job and was always hiding from the landlord.

It's the kind of show it would never pass if it were to be filmed on this date, but we grew up watching it and learning to love it, in the same way we loved racist cartoons by the Warner Bros. or those old episodes where the Flintstones were heavy smokers.

I've written applications using Java, Groovy, Clojure and Scala (in that order) and after Clojure, coding Scala felt specially horrible (yet another syntax to learn! ++: \ ~> and so on...).

Maybe Clojure feels odd for a few hours when coming from C-like syntax, but it becomes so obvious later on. I remember I felt terrified by the parens because I had not written anything serious in it.

Point them to some coding guidelines for the language/platform which you're developing.

For Clojure development: https://github.com/bbatsov/clojure-style-guide

For Scala: https://github.com/alexandru/scala-best-practices/ or http://docs.scala-lang.org/style/

I've laughed a lot by looking at the achievements I've unlocked with my Git repos using Acha: https://clojurecup.com/?#/apps/acha ... My submission to ClojureCup was a simple feeds reader: https://clojurecup.com/?#/apps/friendly

Old LG with Cyanogenmod :-)

In case anyone is looking for a good HOSTS file to use as a template: http://winhelp2002.mvps.org/hosts.htm

Location: Santiago, Chile

Remote: Yes

Willing to relocate: Yes

Technologies: 10+ years of web development experience using Java, Groovy/Grails (2y), Clojure (1y), Scala (1y), Ruby on Rails (2y)

Resume: https://goo.gl/Hkycfo (Google docs link)

Email: Click on my username to see my HN profile and links to my Github repos and LinkedIn profile

I created a free mini-book (in Spanish) about development and packaging of desktop applications for Ubuntu, including examples in C, Python, C# (using Mono) and Java. It's outdated now, probably easy to update to cover some of the latest changes.

https://github.com/dfuenzalida/desarrollo-ubuntu/

Also, long ago I used to download files which were too large to be transfered to another PC over the network, some even didn't fit the USB thumb drives I had at hand; so I created this desktop app which splits large files into smaller volumes, which you can copy around easier and then use the same program to join the pieces and get the original file.

I was very happy to receive requests from other people who contributed with traslations to the UI messages.

It's written in Python (not very elegantly) and I haven't touched it in ages:

https://github.com/dfuenzalida/gtkfilesplitter

Finally, another small project: a plugin for the gEdit text editor which shows the git branch of the file being edited (if any). It should still work in the most recent GNOME desktops, but I do most of my editing in other text editors now.

https://github.com/dfuenzalida/gedit-git-branch-statusbar

There are two things that pop to mind:

You can motivate or coerce your team mates to improve their skills so they all benefit. You can even ask your team leader/boss to be the lead of an initiative at your place to use better tools or technologies so that the productivity will increase. If you get an OK you'll even have an opportunity to spend some paid time doing something which will keep you sharp and improve your daily experience.

If you think you can't get the above to work or that you're way beyond the skills of your team, look for another job with better conditions.

I agree specially with #5. One of the aspects I was at fault for a long time was avoiding conflict and saying "OK" to all requests at work. There will be many times in which you will be asked non-sense or completely wrong tasks and you're completely entitled to say NO. Speak why something is not well planned or conceived or just plain wrong. Just by saying NO you'll cut a lot of crap you shouldn't accept.

"Good Math: A Geek's Guide to the Beauty of Numbers, Logic, and Computation" by Mark C. Chu-Carroll

"Seven Databases in Seven Weeks: A Guide to Modern Databases and the NoSQL Movement" by Eric Redmond and Jim R. Wilson

"The Joy of Clojure, Second Edition" by Michael Fogus and Chris Houser

The invtro to the NVScene party this year was very stylish and featured music from Dune/Orange: https://www.youtube.com/watch?v=TYOBq4NLjtY

From Chile, and way above the mean, something like 4x or 5x.

Jobmote has a curated selection of PHP jobs published elsewhere: http://jobmote.com/tag/php

While I understand the problem this solves, the landing page doesn't express confidence: "Reasons to use this template to pdf solution" should be just "Why using Template 2 PDF?" or just "Why" ... the reasons should be very brief:

* Your end users will be able to modify layouts themselves

* Minimal effort required for software developers

* Business stakeholders will obtain sharp, professional-looking documents, sooner

Minimal changes:

* Change "Features:" to "Features"

* Use "PDF", all in caps, consistently.

The UI theme is screaming for something more end-user friendly such as http://bootswatch.com/lumen/ or http://bootswatch.com/flatly/

Also, I feel the landing page could benefit from a layout such as this: http://getbootstrap.com/examples/justified-nav/

I felt the same way as you until I actually tried Clojure. In a few hours all my rejection of the parens dissapeared because I finally understood.

Try solving a small problem in Clojure (a code Kata, or a problem from Project Euler) and you'll see those aprehensions against the parens will go away.

Nowadays I'm having trouble to accept the syntax of other languages, eg. Scala :-)

looks awesome! ... best of luck

Coming from a Java and Groovy background it took me a while to "unlearn" and I think this is what happens to you.

If you spend more than a few hours on Clojure (maybe you can create a small toy project) it make much more sense.

I'm experiencing quite the opposite, I'm learning Scala now and it all feels too cumbersome, and even the syntax of Scala bothers me now.

In job #1 (5+ years remote): features and bugs have no formal platform, mostly wiki and sprint planning in spreadsheets. Ocassional phone calls but mostly Skype meetings. Knowledge base: dokuwiki. Code hosted on Bitbucket. Cisco compatible VPN (on Ubuntu: network-manager-vpnc-gnome), Virtualbox, Windows Remote Desktop for accessing servers. Trello (soon) and we used Pivotal Tracker with little success. Server monitoring with New Relic.

In job #2 (remote, almost 4 months in): Features, bugs, release planning, code and some documentation, all in Github. Chat: IRC Cloud or Skype. Calls and screen sharing: Skype or Google Hangouts. No VPN but lots of SSHing into machines on Digital Ocean. Some other documentation in Google docs.

I'm dissapointed. I thought I would find a comment about moot on this post or at least a reference to this image ("trolling is a art"):

http://i.imgur.com/iwmk2vn.jpg