The problem with your choice of name, Moodule::Build, is that it looks like a typo, which just adds confusion, especially for beginners.
How about Install::Tiny?
]]>If I were to redesign M::B now (which is not out of the question, really) I would get rid of M::B::Compat (not because it failed, but because IMO it succeeded and is no longer necessary) and get rid of the by-platform class hierarchy.
]]>I realize programmers aren't commodities, but programmers are imperfect substitutes which means you still have demand and supply effects that are comparable and even the Cato Institute, a think tank I generally disagree with, agrees that supply and demand impact wages (to be fair, they're talking about low-income workers which one might argue are closer to perfect substitutes).
I thought I made it clear a simplistic supply and demand curve isn't enough when I wrote after a moment's reflection it should be self-evident that given the complexities of economies, maybe brandishing an economics 101 graph isn't quite enough to model typical developer compensation packages.. I guess I should think of a better way of explaining that, then. Suggestions welcome! :-)
]]>* Read Tweets from your timeline.
* See who you follow.
If that's the case you need a privacy policy since users signing in with this service will expose you to private data in their Twitter accounts that they might not want to share with you.
]]>And seeing that i have to point out a massive mistake i see recruiters make all the time: Talk about the area, but not about the job. What perl versions are in use, what cpan modules are in use, what source repository, what ticket system, etc. etc. etc. For the linked job, if i'm thinking of the right company, they can't even use CPAN stuff due to CC requirements. That's a massive thing and as a job seeker i'd be very annoyed to find that out after investing time into talking with them.
]]>The reason we post the information the way we do is because of my blog, Overseas Exile. I've been writing for years telling people how to be an expat and move abroad and the company my wife and I are creating is all about helping people do that (well, in addition to consulting and training :)
The people who contact us really, really want to experience life abroad. They're generally strong technically and they know they can do the job, but either they're looking for a chance to see the world or, in some cases, the employment situation in their home country is very dire and they're desperate for a chance to at least earn a living doing what they love.
When we work with a company, we learn a lot about the company, what they're looking for, what they actually need and what they're like internally. When candidates apply, we give them this information and let them decide for themselves if it's something they want to pursue. Some choose not to, but most want us to push forward because they're looking for something beyond "just a job." They're chasing their dreams and we're trying to help them. Thus, we give them enough information to get a sense of whether or not the job is a good fit, but also if their new potential home might be interesting to them.
So far it's been great and the candidates we've placed have been very happy. None of them have walked into a situation not knowing what to expect. For posting to specialty areas, like jobs.perl.org, we'll probably go a more technical route for our postings, but for now, we're focusing on what our candidates are really looking for.
I hope that helps explain what we're trying to do. It's about using our passion for experiencing the world first-hand to help people live their dreams. Eventually we hope to expand beyond IT, but for now we're sticking to our strengths.
Cheers, Ovid
]]>Another thing, i can likely add two more companies to those in Hannover, if you wish you can poke me anytime on IRC about them and i'll let you know what i got.
]]> I am also unclear on your reasoning for the problem. Is it: 1) because you don't like how long the module list is with the extra entries? 2) The submissions of Acme:: and related modules are NOT going into Acme:: like they should.
3) Bandwidth or storage space problem for the administration.
4) They are annoying to look at when looking for "real*" modules.
If it is just the 'noise' of looking at Acme::yourname modules, or the annoyance thereof; then should there not be some sort of filter put in place? (more than what exists today) This would be better than to just annihilate the whole category.
If it is the problem of Acme::yourname:: not being used when it should be, then some new policies may be in order.
If it is the problem of bandwidth, perhaps more mirrors are in order, or stricter checks for duplicate or redundant data. Also checking for data that is not to be uploaded. I realize this is being done to a certain degree already, but there is always more that can be done. I would gladly volunteer my time for such a purpose.
To banish experimentation to some other place when it has been done this way for years is something you can only wish for, it's like wishing for developers to all test their modules correctly, it will never happen. There are deadlines, workloads, and time itself to consider.
To quote Buddy Burden's comment, "In a perfect world, I think I'd love to have one of each" of those.
You are always going to have people that will color outside the lines. I could go on and on but I must cut this short, if you require more information from me, don't hesitate to write me an e-mail message.
* The term, '"real" modules' means something different to each of us. Because of this dynamic, it is not possible to please everyone, all of the time.
]]>