there was a python implementation of something like this in tornado (s3server and s3client), though now I don't see it. Anyone follow that project and know what happened to it?
if anyone wants to port the Ruby script to python, put it on kickstarter and ill start u off with $50. i want a link to my webpage, CompassionPit, on the page for the final tool though. and one on the kickstarter page if ur feeling generous =)
p.s. anyone think we need a developer-tools kickstarter? paul, lmk before i give it to my friends at tech stars
A Kickstarter for dev tools would be a great idea. As well as new projects, it could also be beneficial for large changes to existing projects. Some combination of Kickstarter and bounties for GitHub issues would be interesting.
My only concern would be for the potential drama caused by members of the community who find the idea of paying for open-source development abhorrent.
Why does the script need to be in Python? Isn't Fake S3 just a server that you run and connect to from any codebase? I'm curious because Python is the language I use most, but I could easily see myself writing a Fake S3 in golang or clojure or even C.
I don't have anything against the request, and I would actually be interested in writing a Python version. I was just curious what the motivation and goals would be.
I think I'm not being explicit enough. What would you use a Python version for, for which the Ruby Fake S3 implementation isn't suitable? I'm purely looking for a sample use case here. What problem does a Python Fake S3 solve?
figuring out how to sign a FF extension properly without an https cert was one of the most difficult things i've accomplished in my programming career. :(
Well here's a fuck you back from a dev: my time is finite and everyone wants a piece of it; If I can save an hour a day by never having to think about my database? If I can shave a week or two of labor off a project?
It's really easy to work with. This is why people keep using it.
Back at you boy. I'm a dev. I hate dealing with other dev that wasted my time just because he ain't lover with RDBMS and decided to write more code and add more infrastructure components (that includes message queue unless you absolutely have no choice).
My time is finite. Ops time is finite. Obviously you decided to dick around with mine and Ops. How bout I send you to the QA department to write automation and software tools so you don't dick around with production code?
You can write with any language and any storage systems you'd like there.
Let me guess, you're the guy who makes sure there's a "Senior" in his title and you use django because the docs are so great.
I'm sorry you work with incompetent people. Sounds like you're in a cubicle farm somewhere. While you're in a meeting swinging your seniority around, I'll be over here shipping products faster than your team.
First, I'm no senior. My title is simply "developer". I work with people that share the same opinions. Most of us are in the same page and that's how we build our culture. The ones that aren't don't last long.
Second, I'm not using Django.... and what's wrong if I do?
Third. I respect people around me. In return, they respect each other so we don't throw away the word "incompetent" and to think that we're better than anybody else.
No pirates. No ninjas. No rockstars. No racers (dhh?) as well. Just grown-ups doing their job with a bit of love, passion, and respect. All balanced.
Fourth. I have no cubicle. I work in an open space and I love it. I don't need my special office (I had one a few years ago and it sucks).
Fifth. My project manager attends meetings and deliver mostly good news to us. He's the best PM I've been with (so far). If we have meeting, that's usually when shit hit the fan and we need to have an honest conversation. Other than that, e-mails are sufficient.
One reason Moose rocks for Perl is it gives you the ability to get some stronger type checking in the dynamically typed language.
So yes, I think dynamic typing can lead to debugging nightmares. It just so happens that often the fact that other factors make up for this in many cases.....
If you can model your data in redis data structures it is excellent. Keep in mind that there is no preferred mechanism for operating redis when data is larger than ram. There is vm and diskstore, both deprecated by antirez, and a focus on data sets that fit in ram.
If you can do both of those things, it is awesome.
I think you're at the phase where you need practice and experience mostly. Either get a job on a team that's cranking out projects, or go freelance and ship a few dozen sites. You'll start to get some insight into the bigger problems around handling clients, cash flow, project management, etc.
I'd also recommend tornadoweb.org - there are some nice demos included using moderately complex javascript in the browser and python on the server. I'm thinking in particular of the chat demo, which was invaluable for me in understanding how ajax apps work.
Really though, you need to just ship a few projects; the frustrations will clear up and you'll be more accurate in estimating how long things should take.
I'm a professional python webapp guy and I like MongoDB better for the same reason. :) You might find tornado nice!
Some advice on turning this into a career: learning CSS and HTML is very useful, but there's (relatively) lots of jobs where you can program services for the backend and work with a frontend guy who's doing the design work and the user interface. Often for this sort of job though, the people hiring will ask you algorithm and data structure questions.
The other path you can take is really studying graphic design for a bit to train your artistic eye - if you can make pretty nice looking websites, and code up the backend to make them do interesting stuff, you're in a great position to go freelance / solo and build an app on the side.
And lastly, a third path: start writing a lot of javascript! It's getting used more and more, and a lot of the front end guys who "know javascript" are kind of shitty programmers, so there's a good pool of those sorts of jobs available.
I'd downvote if I could. If you have to tap a guy on the shoulder to tell him is code is broken, you're not working with a professional.
Distributed teams are glorious when you weed out the jackasses. And in the meantime, remote guys are comfortable with much lower salary. That seems useful for a startup trying to keep costs down?
