alch-

In the menu, you can manage which calendars are shown.

I second that, recurring events aren't very interesting to me, and they crowd the view (even when just looking at today / this week). Would be great if they were somehow less prominent.

Awesome work though, I love it!

This. Awesome service, but pleasefortheloveofgod don't let people run arbitrary code inside Docker, unless you don't mind them getting out into the parent OS and messing around. You want VMs for that. (Yeah, that's much more resource intensive. Safely running arbitrary code is hard.)

That, sir, is totally awesome. Well played.

Call me a starry-eyed idealist, but

> The iterative bloat during development can happen for so many reasons. (Numerous changes in requirements late in the project,

... and people not cleaning their mess up afterwards;

> many developers working on numerous modules,

... without proper coordination, or, without the drive to keep things clean (i.e. proper manners);

> design for flexibility and expansion that are never used,

... and never cleaned up, i.e. left there to rot by the people who put them there;

> going too far down a path that turns out to be more work than an alternative)

... and not cleaning up.

> Once a program has been in production for a while and its use cases are more well defined it becomes easier for a single person to swoop in and rewrite it in a far more conscice way.

I think it's always easier for the guy/gal who wrote something to clean it up than for the next guy/gal, who doesn't know the code or its history as well.

Really, this is all just people not cleaning up (or being allowed to clean up) after themselves.

Now if we could all just be nice to each other and hold hands..

> It's a very painful way of earning money

But.. strangely fun, in a twisted way? I love a blank canvas or a well-written codebase as much as the next guy, but I find that fixing "legacy"[1] codebases can be pretty enjoyable.

Slowly figuring out and fixing a "legacy" codebase, to me, is basically solving a giant, complicated puzzle that was left for you by your predecessors.

Granted, you're mired in evil gunk from the past, but every time you figure out a small piece of the garbage and refactor it into something nice, you get to feel awesome. Of course, this assumes that you've convinced management that the codebase must be tamed[2] and that this will take time; otherwise you're just fighting with your hands tied.

Then again, maybe I'm just a masochist.

[1] "Legacy", because people don't like it when you call it "evil gunk from the past that must be destroyed".

[2] And it must indeed be tamed, because otherwise it will just grow more and more evil until development grinds to a halt. If management understands this, they'd be crazy to choose the "let the beast grow" option.

Seriously, did you read the description? It's just an "other people who like x, also like y" system, which I happen to think is pretty awesome. If anyone takes this site as investment advice, well, duh, don't. It isn't, and that's okay.