| Time |
S |
Nick |
Message |
| 12:00 |
|
pdurbin |
dotplus: so http://projectsthehardway.com looks fine and the discussion at https://news.ycombinator.com/item?id=9733401 is interesting enough but no one seems to be reminding people to scratch their own itch, as I did the other day: https://botbot.me/freenode/pyladies/msg/42389346/ |
| 12:01 |
|
pdurbin |
that said, if people are looking for a project and would like to hack together an implementation for addressbookmvc that's just fine with me :) |
| 12:03 |
|
dotplus |
I think the whole idea of projectsthehardway (at least in my mind, I don't claim to know Zed's:) is for people who cannot find their own itch (or their itch is too difficult for a novice, which was often my case in the past) |
| 12:03 |
|
pdurbin |
oh. maybe that's just the impression I'm getting from the chatter on hacker news |
| 12:04 |
|
dotplus |
but I agree that prefacing it all with "the best way to learn is to scratch (the simplification of) your own itch" would be a good idea |
| 12:07 |
|
pdurbin |
couldn't hurt. what I was realizing the other day is that stuff like "scratch your own itch" is just part of my vocabulary but people who are just getting into open source may not have heard of it or know where it comes from |
| 12:08 |
|
pdurbin |
but I get it. early on I made lists of possible projects I could work on |
| 12:10 |
|
dotplus |
yep, that kind of entry in your "vocabulary" is what people are talking about when they refer to why it is difficult for experts to teach novices: lack of shared terminology/background/experience |
| 12:11 |
|
pdurbin |
that's why I linked to catb |
| 12:12 |
|
pdurbin |
meanwhile, debate over the spec rages: https://github.com/pdurbin/addressbookmvc/issues/4 |
| 12:13 |
|
pdurbin |
:) |
| 12:13 |
|
dotplus |
I remember reading the jargon file straight through the first time I came across it |
| 12:14 |
|
dotplus |
yeah, I'm going to comment on #4 |
| 12:16 |
|
dotplus |
although esr is a jerk, I'm glad that he collected/authored/published/made visible various works that helped me:) |
| 12:20 |
|
pdurbin |
yeah |
| 12:21 |
|
pdurbin |
I link to the jargon file from http://sourcefu.com |
| 12:56 |
|
dotplus |
btw, if this project takes off, the line that shows the repo's code coloured by language is going to be interesting:) |
| 12:56 |
|
dotplus |
and we really need a new name |
| 13:14 |
|
pdurbin |
dotplus: please add some ideas to http://www.tricider.com/brainstorming/35DVEKere5x |
| 14:24 |
|
pdurbin |
interesting discussion about bytecode: https://plus.google.com/+MarkLewis/posts/FuJmn9QFc1p |
| 14:37 |
|
dotplus |
oh, sorry I should have squashed first. |
| 14:38 |
|
pdurbin |
I have lots of comments to make anyway. :) |
| 14:38 |
|
pdurbin |
dotplus: thanks! |
| 14:39 |
|
pdurbin |
talking about this, of course: Draft Spec by dhutty · Pull Request #12 · pdurbin/addressbookmvc - https://github.com/pdurbin/addressbookmvc/pull/12 |
| 14:40 |
|
dotplus |
I'm sure it's not in final form, hence "Draft". But I figured since I asked for a spec, I should start the ball rolling. With Code. otherwise I'm just bikeshedding:) |
| 14:44 |
|
pdurbin |
heh. sure. I agree with aditsu that an API should be optional |
| 14:44 |
|
pdurbin |
also, I think I use a long rather than an integer for id |
| 14:45 |
|
pdurbin |
and I don't think we should require SQL |
| 14:45 |
|
pdurbin |
what we should require is server side persistence |
| 14:50 |
|
dotplus |
I agree about persistence, I suppose I could have made that clear. Perhaps, we should move that to a 'hints' section - as in "if you want to use SQL for persistence, here's an example so you name consistently". but that was a convenient way for me to specify |
| 14:51 |
|
dotplus |
We can say "Even if you don't want to provide an actual API *service*, please make your implementation behave as descibed in the API doc below, so your implementation can be easily compared against others" |
| 14:52 |
|
dotplus |
Maybe we should change the word "Specification" to "Implementation Guidelines" |
| 14:58 |
|
|
aditsu joined #sourcefu |
| 15:29 |
|
pdurbin |
no objections |
| 15:43 |
|
dotplus |
btw, my sql example was for sqlite, which like SQL-92, does not include LONG. |
| 15:43 |
|
pdurbin |
oh |
| 15:43 |
|
pdurbin |
I'm thinking about the JPA side. |
| 15:43 |
|
dotplus |
JPA? |
| 15:46 |
|
pdurbin |
searchbot: lucky java jpa |
| 15:46 |
|
searchbot |
pdurbin: http://docs.oracle.com/javaee/6/tutorial/doc/bnbpz.html |
| 15:47 |
|
pdurbin |
Java Persistence API |
| 15:47 |
|
pdurbin |
it's an ORM |
| 15:47 |
|
dotplus |
oh, I can't even spell java |
| 15:47 |
|
pdurbin |
heh |
| 16:58 |
|
|
aditsu joined #sourcefu |
| 18:28 |
|
* semiosis |
uses UUID for row ID |
| 18:30 |
|
semiosis |
so threads dont have to sync to insert :) |
| 18:30 |
|
pdurbin |
not a bad plan |
| 18:30 |
|
pdurbin |
semiosis: someday we'll get an implementation out of you |
| 18:31 |
|
pdurbin |
maybe once all of your friends have made one |
| 18:31 |
|
semiosis |
maybe :) |
| 18:32 |
|
semiosis |
i had a little pet project i was working on a few weeks ago and decided to use firebase, instead of writing any backend code |
| 18:32 |
|
semiosis |
it's pretty impressive |
| 18:32 |
|
pdurbin |
link? |
| 18:32 |
|
semiosis |
backend is dead lol |
| 18:33 |
|
semiosis |
https://www.firebase.com/ |
| 18:33 |
|
pdurbin |
huh, so firebase is the backend |
| 18:33 |
|
semiosis |
yep |
| 18:33 |
|
pdurbin |
here I am writing backends like a sucker |
| 19:47 |
|
pdurbin |
hmm, it turns out performance testing is an art |
| 20:03 |
|
sivoais |
re: the projectsthehardway discussion, I still find it amazing that many other programmers don't have ideas for projects percolating in their heads all the time. There's just so much out there! |
| 20:05 |
|
sivoais |
I started by doing various mathematics problems. I knew how to do it by hand, so why not teach a computer the same thing? |
| 21:15 |
|
prologic |
i'll have to catch up with the GH conversation that's happened while I've been asleep |
| 21:15 |
|
prologic |
sorry :) |
| 22:47 |
|
pdurbin |
some strong opinions, which is fine :) |
