Dyn is looking for a Perl developer to join our ecommerce back-end development team. The successful candidate will work on “nuts and bolts” back-end projects that deliver the functionality and experience our marketing team and users expect. Some familiarity with web development would be helpful. However, this is not a front-end web development role.
Required Skills
Sets realistic expectations and delivers on schedule
Able to focus and avoid scope creep while minimizing workarounds
Enjoys not only writing code to deliver function, but also writing and using tests to validate. Feels a project is complete when the results are proven via tests and understood via documentation
Collaborates with technical and non-technical colleagues to identify and deliver excellent solutions
Familiar with OO programming
Understands the core concepts of relational databases
Enjoys working on complex systems in a fast paced environment with changing requirements
Desired Skills
Able to keep user experience in mind during planning and development
Prior experience with ecommerce
Familiarity with revision control systems (CVS, Subversion, etc.)
I wrote Data::Compare::Plugins::Set::Object (blech, what a mouthful) a couple months into my job at GSI. At the time I wasn't sure what if any their policy was on open source releases, so I was careful to do it on the side and assign copyright to myself. I still haven't found an explicit policy beyond my manager's "just use your best judgment" statement. Maybe that's for the best.
Lots is happening in the Perl Web framework world these days. The threemainframeworks are getting better at a faster-and-faster rate, great screencasts are starting to appear, and — finally — Perl is moving into the cloud, thanks to support from new Platform-as-a-Service vendors like dotCloud.
Now, I’ve been known to kvetch a bit about “Perl in the cloud” once or twice before. But this is not a kvetch. No, no, my friend: this is a “Forget the ode, show me the code” post.
By this time folks know that I've been working hard trying to recruit more people for booking.com. They didn't ask me to, but I do this because I find it fun and I like working with people. Also, if you read my expat blog, you know that I want to help people live and work in other countries. I'm very fortunate that this passion of mine fits very well with my current employer's desire to move people to Europe. Yes, I get paid a bonus for everyone I refer, but I also tell everyone that if they don't want to go through me, they can apply directly to our jobs portal. Extra money is nice, but I'll happily forego that if I can help you live your dream of being an expat.
By now, many of you have seen our advertisement on jobs.perl.org advertising that we're hiring 20+ Perl developers. Many people have speculated as to why. This is to put to rest some of rumors which seem to go around.
Dyn is looking for both junior and senior system administrators with Perl experience. Much of their administrative systems are written using Perl.
Junior System Administrator
Description
A Junior System Administrator is responsible for keeping Dyn’s global IP anycast network available and performing well. Job responsibilities include deploying new systems to production, upgrading existing deployments to handle additional load and/or to address security issues to managing vendor maintenance events and debugging complex network and system troubles. Junior System Administrators should enjoy working in a FreeBSD/Linux environment, be comfortable with scripting in shell (bash), perl, and/or python, and have familiarity with networking equipment from Cisco Systems and Juniper Networks.
I’ve decided this is so important to me that I’ll no longer attend or speak at conferences that don’t adopt and publish a code of conduct. I’ll also be using whatever clout I’ve got to encourage conference organizers to adopt and publish anti-harassment policies. […] So why, given the issues [with codes of conduct that] I outlined above, do I take this so seriously?
He makes the point, but does not emphasise it enough in my opinion: the code of conduct is not there to communicate to attendants how or how not to behave (in which capacity it is superfluous with the well-behaved majority and ineffective with perpetrators): it is there to reassure members of minorities that they will be heard and their concerns are understood.
The first episode detailed how to install and get your first Mojolicious Lite app running, and the followup continues the process by explaining how to use multiple types of placeholders, http methods, and formats to give you more flexibility in your lite apps.
You can download last version from sourceforge. If you are on Windows you need Strawberry Perl, just unzip it and click on pni.exe ... if you are on Linux launch the pniguitk script ( but you will need Tk installed ).
Rob Hoelz, the leader of our software team for YAPC::NA 2012, is holding an Act workshop from 5pm to 7pm at the Essen Haus tonight. Don’t worry if you can’t make it for the entire two hours. People are free to come and go as they please. But if you want to learn about how you can help enhance Act for YAPC, then you should definitely try to make it.
Bring a laptop with you, preferably with Perl already installed. If you don’t have a laptop, then we can buddy you up with someone that does. Rob will take care of the rest once you arrive. Hope to see you there.
NOTE: These are the two hours before our normal MadMongers meet up in the same place, which starts at 7pm. Feel free to stay for that. Jesse Thompson and I will be giving dueling talks about Data Munging where we will show you how to extract data out of nearly everything.
Last month we kicked of the meetups for the fledgling Bangalore.pm group. Our first meetup in July was attended by 3 devs including myself to kick things off, this saturday we had our second ever meetup of Bangalore.pm.
The meetup was attended by Venkat(wolf), kumar ravish and yours truly from the first time and one new member in form of Krishna Abbina from my team at work. We met up at Legends of Rock at Koramangala,(the place serves delicious cheese bites)
We mostly talked about Perl and its application to our daily chores. Each of us come from a diverse background w.r.t. what we do with perl and it made for some very fruitful discussions and KT! :)
That's the number of report submissions we saw during the 31 days of July! This biggest monthly submission we've ever had. Just over 40,000 reports more and we would have broken the 1 million barrier. Considering it took 9 and a half years to reach out first million milestone, the fact that we're now seeing nearly 1 million a month is just staggering. I've stopped posting about passing each million mark as its becoming to frequent. You'll have to wait for the 20 millionth report (expected about Christmas 2011 at the current rate) for the next notable post in that regard.
So, a few days ago, I intended to post a paragraph of metablogging, and then get on with introducing a project. Then I was going to post a few paragraphs. Then I actually write it, decided it deserved it’s own entry, and posted it … and decided that I deserved a break. So here I am, a few days later…
Java::Bridge’s intent is to be a way to use and control any arbitrary Java API you want, from inside of Perl code, without requiring the author of Java::Bridge (IE me) to have considered your use case in advance, or having to have a Java compiler on the target system. (Or, for that matter, a C compiler. Preferably, at all.)
One of the things we’re toying with for YAPC::NA 2012 is the idea of an unconference track. The idea is that we’d provide a whiteboard for people to write out ideas for ad-hoc presentations at the beginning of the conference, and others would sign up to attend those ideas. The topics could be about Perl, CPAN, or something completely unrelated. We’d provide a room with a projector and a whiteboard, specifically for this track. The most popular ideas would be given time slots.
What do you think of this idea? Is there room for an unconference track at YAPC?
I think you'll agree we've come a long way since then, thanks to the awesome community and user base built up around the project since then.
In these two years, we've had countless valuable contributions from a large list of contributing users (see the list on the about page), gathered over 300 watchers on GitHub, had 84 people fork the repository on GitHub, had 620 pull requests submitted... amazing stuff.
We've seen Dancer presented at various conferences including FOSDEM, OSDC.fr, the French Perl Workshop, the Bulgaria Perl Workshop, PyWeb IL (an Israeli Python group).
We've seen screencasts on using Dancer (thanks Gabor!), we've seen Dancer discussed plenty within the Perl community with plenty of helpful suggestions.
This post is for users of Marpa's Constant Ranking Method.
You are using the Constant Ranking Method if you specify
the "ranking_method" named argument of a Marpa recognizer,
with the value "constant".
If you're not using the Constant Ranking Method,
you can stop reading here.
Marpa::XS 0.008000 is the last release that will support the
Constant Ranking Method.
In future releases of Marpa, Marpa::PP, and Marpa::XS,
the Constant Ranking Method may be removed.
At a minimum, it will behave differently
at the interface level.
Marpa is alpha but previously, whenever I've changed the
documented behavior of an
interface, I have kept backward compatibility.
As alpha development ends and I approach a beta release,
I am forced to be more ruthless.
I will be changing or eliminating the Constant Ranking
Method, and
duplicating its exact semantics
for backward compatibility
is simply too difficult.
With the American holiday of Thanksgiving right around the corner, perhaps it's time to consider what you are thankful for, and hopefully one of those things is YAPC. If so, you can show your thankfulness by marking down on the paper or digital calendar of your choice that you're coming to YAPC::NA 2012 on June 13-15 in Madison, WI. And if you're not sure you can afford it, ask for it as a Christmas present!
Also don't forget that you can bring your spouse or significant other with you to enjoy our Spouses Program.
I originally started DBIx::Class::Schema::Critic as a code sample for a job application, but I thought it was worth releasing and continued independent development. Inspired by Perl::Critic, it's a package for comparing relational database schemas against a collection of best practice policies using the DBIx::Class Object/Relational Mapper.
At mst's behest I converted it from the Moose object system to his more lightweight Moo. But now that I've accumulated a few policy modules I'd like to refactor their commonalities out into roles.
Trouble is that Moo doesn't have an equivalent to Moose's MooseX::Role::Parameterized, and I can definitely see use for that in creating a bunch of similar roles for each DBIx::Class object a policy applies to.
So what to do? Can/should I port parameterized roles to Moo, while avoiding the overhead of a meta-object protocol like Moose's Class::MOP (which Moo explicitly rejects)? Or just make a bunch of more-or-less identical roles that differ only in name and attribute content, accepting the repetition as the price of minimalism?
And BTW Graham Barr last month fixed the linking of licences in the package view. it now recognises gpl as gpl and not as Postgres license and also gpl_1 .. gpl_3 with much more verbose and precise links. Thank you both. Im just the guy who keeps nagging (one more ticket about pause packages status coding is still underway).
