Linell

This would be an awesome feature.

This is my problem with snooze functionality. Not very often would I actually like to snooze. I'd prefer to eliminate the option as a whole and simply set my alarm back for N minutes if I decide to sleep longer that morning.

That also helps a little with the problem of snap decision making that happens so often when it comes to how many times to hit snooze. If you actually have to think about how much longer you can sleep and set an alarm for it, then you're a lot more likely to make a good choice.

I recently read an article about a university using iBeacons to help fans navigate their way around stadiums, among other things. The possibilities for stuff like this are just really cool.

http://msbusiness.com/blog/2014/07/08/ole-miss-offering-new-...

Less of a replacement and more of a supplement.

USA, Remote or Relocation, Full Time Stack: .NET (C#, mvc), NodeJS, PHP Resume: http://thelinell.com/resume/ Contact: tlbonnette@gmail.com

I am graduating next week with a BS in computer science and a minor in mathematics. I've completed two internships and held a variety of software development related positions, including QA lead during one internship. I truly enjoy software development and would love to work for a company that would help me get my career started off right. I'd prefer to stay in the Southern United States, but I can relocate.

A problem that I had when looking for task tracking tools a while back is that the majority are just more complicated than I needed. I needed the equivalent of a whiteboard list on a website.

So I made a nifty little thing I called Millwright [http://thelinell.com/Millwright/]. It's certainly not as "fully featured" as the trackers on this list, but that's why I like it. It's ridiculously simple so that you can focus on the tasks instead of the process.

How can someone who has time and could be that "fit gazelle" get into contributing to open source?

I have tried several times. At least, I've looked at a few of the suggestions on how to get started. All of the ideas don't quite work, though. Namely because most of the suggestions are things that I've either never even heard of or that I do not use. The gardening approach mentioned not long ago on this site seems very good for beginners - but I feel that just jumping in and starting with this could be a bad thing if the organization already has some sort of system set up.

For example, I have used Express. I don't really understand it well enough, and I've never had reason to, jump into the source code. There are only ten open issues. For just about every open source thing I've used, this is the case. Am I just doing something wrong?

While I've never used a Linux VM on Azure, I can say that every question I've had was answered quickly and extremely thoroughly. I've never ran into anything that support was unable to help with.

Someone definitely should. For those of us who aren't super experienced, it would be good to hear both sides of the story in the same place.