635 karma · joined August 27, 2011
If you're talking about Ubuntu, I can attest that the default PM there is several versions out of date for a lot of things, and thus to get the version you'd expect, you're forced to install by hand.
Also, even using the PM version, didn't you get a warning when you started the server? I thought Mongo threw up a warning at start time about this exact issue (the 2GB limitation, not the silent failures)
Yes. Without question.
Is this his own fault for not reading the documentation and understanding that he should have opted for the 64bit version outright?
Yes. Without question.
Always get cash, and take equity if it's offered (so long as there aren't any strings attached).
Cash will pay your bills today
Lotto tickets may never pay you a dime, and can be a drain on you emotionally if you're constantly expecting one to pay off.
There are third party takes on this system as well, but I've never tried any of them.
Various places i've worked for have had a very similar (to each other, not to rails) approach to doing versions.
First and foremost, you need a core set of scripts that you are always updating to be the "latest", so that you can very easily spin up an empty db + required static data + any bells and whistles you wanna throw in (like a default user account, for example - although you don't want to run that script on production, clearly).
Then you need another set of scripts that you keep in directories named for their version. Those scripts either reference the scripts inside of your core script directory (for example, if in release 1.4 you're adding a new stored proc, you'd define the proc in your core folder, and in 1.4 you'd have a script that runs all the 1.4 changes, which references the file from the core location), or comprise the DDL changes you're making that are now reflected in your always-updated core scripts (for example, if you modify a table, you'd update the core script to have the latest definition, then add a modification script under 1.4 that just does the diffs to that table)
The most important piece here is an environment to run things in that will handle making changes in a transaction, and rolling things back if something fails (so you can safely do your updates and recover without putting any database in an incomplete or corrupted state). On Windows, Powershell works fine for this (although PS isn't the best thing in the world, it gets the job done). On *nix, i'd imagine you can accomplish the same thing with a bash script. You absolutely do not want to be running scripts by hand, 1 after another. You should have a light set of scripts built around whatever file structure for your sql files you have, that follows a convention based approach to locating an "upgrade.sql" file, which then invokes the rest of the sql files needed for that upgrade.
Hopefully this approach makes sense as I've described it. It's by no means perfect, but as I've said I've seen it in use in several places, and it seems to work just fine.
If you try to go through his employees by saying you want to redo his website, they'd probably be less susceptible.
Just a thought - good luck, that's a rather noble endeavor of yours.
I've watched that video before, and it's a really great talk on a common problem. I'd recommend it to everyone.
Mine too!
And isn't this the REAL injustice?!
My point was mainly one of self reflection
He didn't name it "Labia" or "Clitoris", he named it after a product that females use for hygienic purposes. I can't really think of a particular brand of male-genital-hygiene products off the top of my head (that aren't also used in other areas, ie: hair trimmers or washes), so I went with something as similar as I could that served a single unique purpose.
I'm not saying I'd see a product named Jock Strap and say "Wow, that's a great name!". My point was, the initial shock value of the name wore off once I realized I wasn't in the third grade anymore and it was just the name of a product that ~50% of the worlds population makes use of on a regular basis. A shock value that would not have been there for me had the name been something like Jock Strap, which would be a product that I'd be more comfortable making quips and jokes about.
Also, "Flower" and "Butterfly" are feminine words now?
Then I realized I need to grow up, as I wouldn't have batted an eye if it were called Jock Strap or something inherently male in nature.
Bit of a disconnect between the "meaning" of the name and the logo, but again, part of this may boil down to my own level of discomfort/unfamiliarity with products that women make use of on a day to day basis.
Or maybe the person who made it is intentionally going for something that will cause discomfort and discussion, to further spread awareness of his product.
tl;dr; Things that initially make us uncomfortable may end up revealing a little something about ourselves.
Neither
Do some research and find which one works best for the product you envision building. If they both sound like a good fit, go with whatever one you can get help with more easily, since you mention (in the comments) you're not a programmer.
Cool to look at? You betcha
Not everything needs to be a technological marvel
The problem isn't that people don't respect a developers time (ok, some don't), but rather that when you lack proper IT infrastructure, the devs are the first likely choice to be pinged for any kind of computer related issue.
If your devs are constantly getting "My printer doesn't work" / "Why can't I get on the wifi?" style problems, you need to get a systems/network administrator in house to run interference on those types of issues.
If it's other business concerns, thats a tougher one. Sometimes they'll need to be pulled aside for a specific task, or to weigh in on certain decisions from the perspective of the team building and maintaining the code base, but ultimately it's the person in charge of the team who needs to make sure his team members aren't being too distracted.
You are doing a great thing, and I applaud you
Build until you hit a wall, then figure out why you hit the wall; Did you take a wrong turn? Did you a ladder? Or maybe a Hammer?
Build, build, build. Keep learning. Learn another language. Do things out of your comfort zone. Once you think you know something, try to take another step forward.
Don't be afraid to fail, don't be afraid to ask for help.
Above all else, just keep going. And never listen to people who discourage you because you aren't doing it "right".
Start with Python, or Ruby, or Javascript. Something simple. If you're a fan of Windows, take a look at C# (which you say you've had a semester of already).
Start S M A L L. You say you try to build things that are over your head. Don't do that. Build things that are just about your level, while still providing a challenge. You're not going to come out of the gate with something like Kenneth Reitz' "Requests" framework. You're going to have years of learning and experience ahead of you before you can produce work like that (unless you're a prodigy, which almost none of us are).
Most importantly, do not give up. You are not stupid or incapable of programming if you hit a wall and can't seem to get by it. We all hit these walls, at every level of our craft. The issue is recognizing when you have the ability to climb the wall, to blow a hole through it, walk around it, or just go back the way you came and pick another path.
You could try applying for unpaid (or lightly paid) internships as more of a learning experience. If companies don't think you'll be a drain on resources, I would imagine certain companies would love to have someone who is eager to learn hanging around to take minor tasks and to be mentored for a few hours a week. The key there is finding the right company with that kind of time/support.
Best of luck.
And thats where it lost me. No FB account, no way to continue.
The next time you do something like this, consider doing it in a way that everyone can actually participate in. Interesting idea, but fails at the end for people like me who are unable to get past a certain part.
Oh, everyone else already covered it.
The breakers in your home breaker box operate the exact same way. A 20A breaker will trip once you exceed a certain threshold, which I believe is 16 or 17. They're rated to go to 20 by the factory, but to prevent problems with overloading and causing fires/explosions/etc, they purposefully break at a lower threshold.
So this isn't just a colo price scam thing, this is the way the world works.
Something about CSS prevents me from really grasping it and using it with any real skill. I mainly live off of designer friends and things I can cobble together with the help of google.
Good luck!