simopaa

Apparently https://xscode.com scrapes public github profiles and makes it look like they are ready to "chat". Without permission, naturally.

Check https://xscode.com/profile/<yourgithubprofilename>

The page includes an email to contact if you don't want your data to be shown.

I recently was struggling with an design/architecture issue all day, and when I was finished I thought about writing down some thoughts about the what/how/why aspects of my solution for future reference. I then stumbled on the term 'developer diary' for this kind of thing (for ex. https://www.smartics.eu/confluence/display/PDAC1/Developer+Diaries), that apparently some software developers hold in high regard.

I will be trying to keep my own (though a bit more light/free form than that in the link) in order to bring a bit more structure to my day-to-day.

Do you have any experience with developer diaries? Have they helped you become a better developer, and if so, what kind of effects did you notice?

For the past three years I've been working part time (0 hour contract) as a developer while completing my studies. Now that I'm graduating, I have a choice between going full-time or continuing with the current style of contract.

I've been loving the freedom that the 0-hour gives me - and the boost in productivity compared to the 8-hour day - and the possibilities in improving myself in the spared hours. However, considering our current projects, I would still probably keep putting in about 6h/day.

There are benefits in full time as well. If I were to take it, I would gain access to paid holidays (meaning Christmas, Easter etc. I do get actual holidays the same as everyone else) and sick-days, as well as maybe improved guarantees and rights. The company argues that it would be easier to manage the bureaucracy as well as estimate the times for each project.

If anyone has had any experience in a similar choice, or has any opinions either way, it would be most appreciated.

I've been increasingly interested in pursuing a career (or at least doing some work) at open data, by which I mean ie. opening and managing government data and APIs.

I think that one should be adept at least in different API techniques and database systems, but what else would be good additions to an open data expert's toolbox? Data visualization and other ways of making it not only accessible - but understandable - would also be of value?