Lead Engineer at PAX Labs, we just open-sourced some Java utilities i wrote in the early days building service oriented architecture on dropwizard: https://github.com/PaxLabs/java-utils
A few things in there:
* `HibernateQuery` - wrapper around hibernate jpa implementation, because using the jpa criteria api is verbose as hell (seriously, even for java). Coming from having written Django, I wanted the ease of using Querysets in java
* Makemigrations - this seemed to be a missing hole in the java ecosystem. Our contractors were hand-writing sql migrations and using some framework that just ran them. Liquibase exists for managing migrations, hibernate can generate the schemas. This library is a dropwizard command to generate yml to migrate the old schema to the new one.
It's not a tradeoff. The reason we like quality code is it saves time in the long run by being clear, easy to change, less error-prone, etc. If you expect to be employed in 6 months, you should be refactoring and putting care into the quality of your code. It's hard at first, but I'm at a point where I'm the most productive engineer and I work the least amount of hours - because my code is there to help me, not hurt me.
I've been working on a similar project in my spare time to create tools for interactive technical blogs [1]. It's funny, in the past day I've seen two projects that I would say have the same goals as me, idyll being one of them.
What are the possibilities around contributing to idyll? Building on top of it? Is it as simple as writing my own components?
I'm specifically interested in uis to define data structures. One of the more annoying things I found working with d3 to create graphs (as in graph theory) was defining the graphs procedurally, so I built a ui to define graphs graphically.
I'm a regular Google+ user and I find it incredibly valuable. The fact that there are fewer people on there is actually an asset - the people that do use it do so because they have some topic they're interested in that they're discussing with other interested parties. There's a lot of mathematicians, scientists, and authors. In general, the average g+ user is much more knowledgeable than on any other site.
Also, the actual features are super valuable. You can create collections with varying levels of privacy for your posts. I use some private collections to take notes, and post more well thought out content in the public versions of those collections. The collections help me organize my thoughts, and I can see different ideas emerging over time. I have a collection to talk about software engineering practices, for example.
Also, being able to create private communities is nice. My wife and I have a private community where we share things about our daughter - photos, things we want to remember, things she's learning.
This is great content! Do you mind if I ask how you made it? Specifically the interactive demo? I've been working myself on a project[1] to explore tools for interactive demos, but so far I've just done one with a toy piece of content.
The prominence of metaphor to human cognition was put forth in Metaphors We Live By, by Lakoff and Johnson. A fantastic book. Anyone interested in the line of reasoning in the article here should read it.
I also found that interesting. i had to reread the chsrt to be sute, because my bias was that older women would find it more innappriate. I have two hypotheses about what's driving that:
1. Harrasment is more well-known now, and less tolerated
2. The call-out culture today doesn't actually prepare people to interact with members of the opposite sex as adults.
I believe (2) is more likely to be true. What I mean by two is that, with young people being encouraged to "call out" any interaction they might find slightly uncomfortable, they develop a sense of fear and wariness around cross-sex interactions, and can't manage their feelings of attraction.
A few things in there:
* `HibernateQuery` - wrapper around hibernate jpa implementation, because using the jpa criteria api is verbose as hell (seriously, even for java). Coming from having written Django, I wanted the ease of using Querysets in java
* Makemigrations - this seemed to be a missing hole in the java ecosystem. Our contractors were hand-writing sql migrations and using some framework that just ran them. Liquibase exists for managing migrations, hibernate can generate the schemas. This library is a dropwizard command to generate yml to migrate the old schema to the new one.
* generic pagination bundle