Aside from the awesome writeup that Hector provided, I just wanted to call this out:
> It works great as a fast way to get your app up and running
It's a really neat and useful tool for prototyping. Obviously as you start to get more and more business logic that should be in your backend, you may want to migrate to your own backend, but if all you need is a simple key:value store, it's great. Heck, it even does files, auth, email, etc. You can take a prototype pretty far before reaching the edge of its usefulness.
There are lots of frameworks for game development, but the problem is exactly in what you've described: rails. You can only get so far within the constraints of those frameworks before you need something it just can't do, and have to develop yourself. Depending on the framework, this may not even be possible (which is what leads to creation of new frameworks).
With that said, a lot of great (albeit typically somewhat simple) games are made with frameworks. When I when to a few game jams back in college, we typically started with something so that we could have a "complete" game by the end.
This article at one point proposes splitting content into separate apps. I'm unsure of the end goal of this; I guess that it's trying to provide a clearer divide for users, allowing them to filter content in a sense. It seems like this would be better solved by filtering better within the app, separating apps is just going to lead to more confusion, imo.
It had been over a year since I installed FileZilla, but I re-imaged one of my machines and needed it. Hopped out to SourceForge not thinking too much of it (not a fan of the UI and ads within, but I know my way around to avoid them at least). Started the install and it wants to install MacKeeper. Can't begin to describe how disgusted I was. I wasn't sure if that was caused by SF or FZ, though.
Oh yeah, I totally understand that, was just offering an alternative as a non-ideal workaround. I have the same set up for a service I offer, primarily because (afaik) it's hard to beat S3 pricing.
I don't really care for the tabs actually, haha. I was surprised they made that choice when I first used it on there, after getting used to OSX.
But the UI aside, the problem I was having is that it would just entirely hang the app if you had a large number of changed files or large diffs. This was about three months ago, so it's possible the performance problems have been fixed.
This is actually a really good point, and perhaps one against OSX. I'm not really a Windows guy, but I can keep a partition with Windows super easily for the things I do need Windows for. I can't do that from Windows to OSX. That's not Windows fault, because Apple prevents you from doing so, but if you're on Windows, you can't (concurrently) run OSX.
I think you mean #5, and while I've had good (limited) experience with Sublime, but one of my other favorite tools (SourceTree) is absolutely horrendous on Windows. Just a single data point.
It would be slower than on disk for sure, so if that's a concern, it wouldn't be a good choice. If the poster is just storing off results, pushing it to S3, or even potentially a document database could be a logical choice. They said they're just using it for occasionally re-parsing at a later date, so immediacy doesn't seem like a huge concern. Just a thought, at any rate.
Couldn't you potentially push that aspect elsewhere, into a data storage solution like S3 or something (not sure of the cost efficiency, not a huge cloud guy myself). Then you'd just be utilizing the DO server for processing. It would have the added benefit of allowing you to scale your crawling horizontally if you wanted, as all your servers could have access to the same set of data.
To both you and exelius, got it. Missed the part about there being a cash incentive not to sue. I thought it was just agreeing with no incentive on your part.
Could someone explain why I would want to sign an "agreement not to sue" contract while being fired? It seems like I would need to take some time to evaluate the situation externally, rather than just agreeing immediately. Asking me to sign that while in the process of being fired is making an awkward situation even more awkward. Perhaps I'm not looking at this correctly?
I'm not arguing for time sheets, or even any form of time tracking. Just that as a team, if we agree to show up to the office at a time, and someone isn't there then, you'll have feelings about it.
The part about teams that operate via timesheet is a bit of a stretch, imo. At least in larger orgs, I don't see the "need" (read: keeping middle-managers employed) for time tracking ever going away.
While I agree with the sentiment that time tracking is pretty useless, I don't think it's going to stop.
Sending them home for being 6 minutes late is totally overkill (unless it's something that has occurred many times, and there have been warnings).
Quitting for being sent home for a day also seems like an extreme reaction, though, especially if you like the job otherwise.
I wouldn't call it time-fetishism, and I wouldn't say it's something limited to "older folks," that seems particularly unfair. I'm 24, and when people couldn't be bothered to show up on time, I was bothered by it as well. And I'm a developer. I know that it's not vital that "you be in by x-o-clock or no work will be done for the day," but it definitely creates a stigma toward the individual who roles in later than the rest of the team.
Yes, using alternative ports does sometimes work. In the past, I had used NoIP or whatever the name was at that point to route incoming from 80 to a non-standard port. CloudFlare could probably do the same, but then have you defeated the goal of self hosting, since you have a provider in front of your site?
As someone who has no problem reading this (or many of the things linked to by some of the child comments), can you explain what part of it you struggle with? I'm not on a particularly fancy resolution or anything, just a standard, non-retina Macbook. I'm also only 24, so perhaps my eyes are just "still young.
The expected value of slot machines is negative, but there is that slight chance of making a significant amount of money. That sort of "lottery odds" behavior doesn't really work here, imo.
You are correct, for the most part. Even on a smaller team, if you have stronger and weaker programmers, the end result tends to be a functional product. However, I think it tends to create stress on the team, as the stronger programmers feel like they have to pick up the slack and be extra mindful for mistakes made by their counterparts.
I realize that 1/3 is not terminating in decimal, what I meant was that in JS, it seemed to end neatly after x decimal places, which I found interesting. I hadn't tried the operation you mentioned until you posted that, the results are even more bizarre to me. Seems I need to spend some time relearning floating point math to better understand what I'm seeing.
Hmm, so BCD seems closer to what I was roughly imagining (though, I haven't really thought this issue through deeply or anything), but you mention it has shortcomings as well. I guess I'll just have to trust that other people have thought about this, and have determined this to be the best solution, even with its flaws.
I guess I wasn't necessary referring to solving the problem of non-terminating numbers, but more things like 0.1 * 0.2 = 0.020000000000000004 in Javascript, or the very first bug listed on the linked page.
Perhaps what you intend with that statement is that issues like that of 1/3 are a cause for these sorts of issues, but interestingly (at least in JS), 1/3 is terminating, and results in an "expected" value.
I know this is a problem with many programming languages, but why is there not a standard way to precisely represent decimal numbers? I understand the difficulty representing them in binary (well, kind of -- it's been a while since I read about it), but it seems like knowing this, a better solution would be found. Why is this accepted and standard behavior?