lsinger

9 ms·

31.
by lsinger 12y ago
Oh, now I see they actually interviewed John Britton from GitHub on that. I don't buy this completely, though: "But as far as...we don’t have a set, like, this is the way, right? There are multiple ways to use GitHub in the classr
32.
by lsinger 12y ago
Interesting. Interviewee can't use GitHub for their class because the servers probably are in the US: "Copyright is a big issue. For instance, we are working with a novel. In Canada, that novel is in public domain so it can be acc
33.
by lsinger 12y ago
Looking at the challenges, it would be cool if GitHub picked that up and published best practice guides for teachers and also collaborating researchers. Such guides could come from this study and others like it. I remember they're doin
34.
by lsinger 12y ago
It's yours for the taking: http://www.krakenrumstore.com/products/the-kraken-umbrella
35.
by lsinger 12y ago
Awesome, thanks for sharing! A look at a sample issue would be neat though. Right now, I have no clue what exactly will be in the emails.
36.
Sofa.io: an SDK for building e-commerce web apps(sofa.io)
13 points by lsinger 12y ago|0 comments
37.
by lsinger 12y ago
Oh, and nicely wrapped in Fluid [1] as a site-specific browser with a nice icon [2]. [1]: http://fluidapp.com [2]: https://www.iconfinder.com/icons/71619/book_moleskine_notes_...
38.
by lsinger 12y ago
See here for Basic Auth: http://stackoverflow.com/a/13357591/633167
39.
by lsinger 12y ago
I use GitHub's gollum [1] git-based markdown-supporting Wiki for pretty much this. It's easy to add a basic username / password protection. I run it on a Digital Ocean instance that had some capacity left over and have a cron
40.
Ripe for Disruption(jacquesmattheij.com)
61 points by lsinger 12y ago|35 comments
41.
Study: How Projects use Pull Requests on GitHub(gousios.gr)
5 points by lsinger 13y ago|8 comments
42.
Why and how to use Twitter as a software developer(blog.leif.me)
1 points by lsinger 13y ago|0 comments
43.
Stop fooling yourself -- by changing your mind(blog.idonethis.com)
1 points by lsinger 13y ago|0 comments
44.
by lsinger 13y ago
Thanks! :)
45.
by lsinger 13y ago
Well, most of the developers we talked to were professional developers, so they probably were tech-savvy. Maybe the removal of RSS happened so long ago that nobody's really frustrated by it anymore -- either you use a client (CLI if
46.
by lsinger 13y ago
Right, it didn't turn up in the exploratory survey or in the interviews. Well, also we wanted to know how developers use Twitter ... the API I guess wasn't that important at least to the people we talked to. Some said in the ini
47.
by lsinger 13y ago
Awesome, thanks for your interest! :)
48.
How Software Developers Use Twitter(to.leif.me)
46 points by lsinger 13y ago|5 comments
49.
A Short Primer on Dynamic Governance(arlobelshee.com)
1 points by lsinger 13y ago|0 comments
50.
Ground: web framework with JS on client and server, synch, and offline support(gnd.io)
2 points by lsinger 13y ago|0 comments
51.
by lsinger 13y ago
Yes, please?
52.
UML in Practice(neverworkintheory.org)
47 points by lsinger 13y ago|47 comments
53.
On the usefulness of software metrics(ericbouwers.blogspot.nl)
1 points by lsinger 13y ago|0 comments
54.
The truth about code reviews(alex.nederlof.com)
2 points by lsinger 13y ago|0 comments
55.
by lsinger 13y ago
For outstanding research on the meaning of progress in your work, take a look at "the progress principle" by Amabile and Kramer: http://www.amazon.com/gp/aw/d/142219857X/ Gist: yes, progress is essential to feel good about your work.
56.
by lsinger 14y ago
Either I fixed the problem or traffic has simply gone down enough.
57.
by lsinger 14y ago
Nice one. :)
58.
by lsinger 14y ago
Totally embarrassing. I'm trying to get it running again.
59.
On testing culture in GitHub projects(to.leif.me)
37 points by lsinger 14y ago|8 comments
60.
Study: Static Typing Improves Maintainability(pleiad.dcc.uchile.cl)
1 points by lsinger 14y ago|0 comments

More ›