451 karma · joined June 23, 2010
Sometimes it's not like that. There's a lot of friendly people, who encourage newcomers, and realize that if they opensourced something, it's not theirs anymore, it belongs to community. I just wish there were more people who're that friendly and involve more and more team players to get stuff done in their projects.
For instance, i have some feature for my product, that requires extension of the framework I'm working with. My actions are following: check whether it's already done -> ok, not done -> build a simple prototype, proof of concept -> go create an issue / start discussion / show your prototype to maintainers or community.
So, after the last step most of time i was getting stuck. Either I'm doing stuff in a wrong way, but most of commits that were followed by the same path, weren't getting through. First maintainer sees it, says that we won't do it since that's not in our primary field of interest, and closes the issue. Reopening and trying to involve more people into discussion doesn't lead to the success, since dominated opinion was already stated out, and people tend to agree with people they know and trust.
Second approach. Fixing the issues you're facing. You're using some stable version of software (not cutting-edge), and notice that something went wrong. First google request gives you a link to a patch. So, your work is not required anymore. If it didn't, you still should write a unit-test and prove that that stuff was caused by framework, not your software bundle. Having not much or no open source contribution makes that process long. If not - you succeed and provide a patch or wait until someone fixes it in a better way.
Third approach. You don't have any features that you lack, and you didn't face any unfixed issues during development. But you want to pay back to the community, since you're thankful. You go to the bug tracker, and try to find a suitable bug for yourself. Often by the time you come up with a prototype, gurus already get it fixed. So, you're out of process again. You should really dive into that and spend long hours to get to know source code very well first, get acquainted with active people there. It's never been easy.
actually, i like that service way more than any chatroulette-like things. that one actually makes impersonalization before you can see the face of the person. most of time i was getting skipped. now i have a chance to actually meet the person before i get skipped)
nice talking to you :)
Although, having a chocolate bar when working long hours to keep your brain awake works well too. From time to time, i'd say, but not on a daily basis.
Thanks for pointing that out, but i was speaking more of concrete algorithm implementation rather than abstracts.
BTW, if you do want to develop a library to work with classifiers, my only "wish" would be to have a good export/import tools. Most libraries i worked with are using their own serialization formats, so it's quite difficult to import/export data without an overhead. If you write several adapters that could allow people to work with datasets through the adapters, i'm quite sure that ecosystem will get created by other people extremely fast. Some people use mongo, some use postgre, others use files, csv, serialized formats. It's great to be able to continue to use your own things without changes when running that kind of a lib.
Other "wish" thing is to have an ability to run classifier as a map/reduce job, and do it easily :)
it's completely possible to write the code in Scala that would be quite similar to the one you write in Ruby (especially JRuby in that particular case), although Scala allows a lot more, in terms of FP, threading and so on. if you're building a really high-tech startup, and your most important use cases are bound not only to front-end, and you need a reliable base for data processing, manipulation, hardcore server-side, use Scala. if it's going to be just a website with _some_ features that require a lot of processing, use RoR and maybe some Java/Scala for your backend processing.
I can't see any obvious benefits out of using Scala/Lift for mere website building against Ruby on Rails, unless you're making something i was talking in that topic...
his last tweet contains another XSS vulnerability hack: http://t.co/@onmouseover=document.getElementById(status).val... test_nau';$('.status-update-form').submit();"style="background:red"/
using that twitt it's possible to post from your account
There's not much sense to learn another framework OR another way to solve problem. You should concentrate more on a theories that let you do it all yourself: Set, Type, theories etc.
I like the way Ezra Zygmuntowicz explains stuff, and enjoy reading his posts and listening to records of his speeches.
Same thing about Michael Klishin, who used to be in Rails Core. Actually, that's the guy whom i learned from the most. I had a pleasure to meet him in person, and he did teach me tons of stuff. Not specifically-technical, more of vision-sharing things. Those things did influence me as a technical person a lot.
Same thing about Yehuda Katz. I like the way he thinks and ideas he comes up with (most of time).
So, I'd divide it in 2 parts: technical stuff | vision / point of view.
Groovy / Grails is a great thing, as for me too. You get a JVM and a whole lot of Java Libraries accessible from Groovy code, but also dynamic typing and, more or less, lightweight framework. That's if you're already familiar with Java. I think that it's going to be pretty easy for you. There're way more things laying around, such as JRuby that runs on JVM. But that all highly depends on what you're going to develop, or what tools you're most familiar with...
before the vast majority really accepts some technology, early adopters come in. they figure out better ways of doing stuff. until someone has a success story, people doubt new technologies. Ruby brought us a great object model and introduced a lot of perl / php people, or simply web developers shifting from anything else to metaprogramming. probably, until i faced Ruby, coming from .net / java background, i didn't know (that much) about it. neither about dynamic typing.
closure is - yet - another language, that's quite true. we don't speak much of a performance here (even though it seems to be great), hence it does introduce us to functional programming and makes us think differently about objects and persistence. it doesn't mean that you have to quit your job and start looking for haskel / closure / scheme / lisp job. it means that you _may_ benefit just from knowing how stuff works there.
remember s-expressions in Lisp? they nicely fit into .net expression trees, no surprise. smalltalk object model did work for Ruby. you may benefit from traits from scala in your Ruby code. and so on.
so, until there's some success story and bunch of libraries / great codebase / frameworks for development, most of people will stay aside. though you have a chance to get into the crowd :)
i love haml, and sass, since it's just speeds up development several times, improves readability and eases the whole process.
Overall, you may also want to use orm for sakes of interchangeability of your SQL as well, and it certainly gives you advantages.
Im working on a project that involves no orm and uses oracle as a primary data store. Though I don't want to install oracle On my machine but repository idea built-in to project doesn't let me use postgre for development. And yet schema creation involves varchar2 that's simply inaccessible in postgre. Its quite easy to fix but I'd expect to have some kind of a fallback....
In any case, it's a good point that key-value storages are not for every problem, but that's quite obvious. someone said that every time you say "nosql", a kitten dies. so, careful there.