Tiago Matos’ Nest

Imagine you’d like to embed a Mailchimp Newsletter like this one at vendder.com footer or this at the top of one store running on vendder.com and you’d like to translate the error/success messages that output from MailChimp.

Fortunately for you I have the copy&paste code here (Portuguese version).

mce_jQuery('#mce-'+resp.result+'-response').show();
mce_jQuery('#mce-'+resp.result+'-response').html(msg);
}
}
}
mce_jQuery.extend(mce_jQuery.validator.messages, {
required:"Este campo é obrigatório.",
remote:"Por favor corrija este campo.",
email:"Por favor insira um email válido.",
url:"Por favor, digite um URL válido.",
date:"Por favor insira uma data válida.",
dateISO:"Por favor insira uma data válida (ISO).",
number:"Por favor insira um número válido.",
digits:"Por favor, digite apenas dígitos.",
creditcard:"Por favor insira um número válido de cartão de crédito.",
equalTo:"Por favor, insira o mesmo valor novamente.",
accept:"Por favor insira um valor com uma extensão válida.",
maxlength:mce_jQuery.format("Por favor, não insira mais de {0} caracteres."),
minlength:mce_jQuery.format("Por favor, insira pelo menos {0} caracteres."),
rangelength:mce_jQuery.format("Por favor insira um valor entre {0} e {1} caracteres."),
range:mce_jQuery.format("Por favor insira um valor entre {0} e {1}."),
max:mce_jQuery.format("Por favor insira um valor inferior ou igual a {0}."),
min:mce_jQuery.format("Por favor insira um valor maior ou igual a {0}.")
});


Note: mce_jQuery.extend is where the code start.

First of all “textareas” do not have “value” attribute, so the title is a bit erroneous. Nevertheless, let’s get back to the point: updating texarea using jQuery.

I have tried:

$(’#textarea_id’).text(’value_to_update’);
$(’#textarea_id’).html(’value_to_update’);
$(’#textarea_id’).val(’value_to_update’);

and both “text()” and “html()” do the job but none brings you a flawless solution so my advise is to use native Javascript:

document.getElementById('textarea_id').value = 'value_to_update'

Most likely, you’ll do just fine with jQuery but for our translation functionality at Vendder we’re doing some funky stuff on automic updating / reading texareas.

And this is way they so small to such a small target (or able) public.

All items take the following time measured in developer-hours.

2, 4, 6, 8, 12, 16: These increments work for 80% of feature additions.

Anything over 16 hours proceeds in increments of 8 until 40 hours. 24, 32, 40

After 40 hours 1 week of one developers time, start to increase by 12.

This is because anything over a week now has a higher probability of being affected by outside sources now. I can easily shield any developer on my team from outside distractions for 1 week, but its impossible to push off a person entirely after that. You may absolutely need them for something else with a higher priority or deadline.

After crossing 60 hours, I increase by 16 hours at a time.

We usually stop at 120 hours.

Very few projects get estimates past 80 hours anymore, but its not impossible. After 120 hours, we break the project into smaller, more digestible pieces of 80 hrs and under. I recently estimated a very large project at 300 developer hours, but it was really 3-4 smaller projects of 60-100 hours each. With practice you will find natural ‘breaks’ in a project for estimates. Maybe its database, back-end, and front-end. Etc…

via Effective Development » Estimating Resource Time for Web Development Projects.

If you ever cross the line of following more people in twitter that you can handle try:
http://dossy.org/twitter/karma/

Hello CouchSurfers!

On every CS profile, members share their personal missions.  Whether it’s to “take a road trip through Australia,” “enjoy my new job,” or even “figure out what my mission is,” CouchSurfers share their goals and aspirations with the community.  I’m excited to announce that now, everyone can also read about the mission and vision of CouchSurfing as an organization.  Our new statements (available on our About page) provide our community with a common understanding of our future and our values.

Many of you are familiar with our previous mission statement, “Participate in Creating a Better World, One Couch at a Time.”  While this line provided a great slogan for CS, since it was released in 2006 we have realized that we also needed a stronger, more detailed set of directives to provide guidance to our growing group of volunteers.  As CS grows, some members have expressed concern about the future.  Will CouchSurfing preserve its identity as it becomes larger?  These documents are a guarantee that our core values and ideals will not be lost, even as our community expands.

Word cloud from member testimonials
The process began with research.  Volunteers and I hit the books and conducted surveys.  Over time we decided on a plan to create a full set of cornerstone documents, rather than just a new mission statement.  Our vision would describe our ideal future for the world.  Our mission would describe what we do as an organization to achieve our vision.  Our guiding principles would shape the culture of our organization by affirming the shared values of our staff and volunteers.

Then it was time to create the documents themselves.  With a group as diverse as CouchSurfing, finding a vision and mission that could represent the goals of our community was a big task.

We began by interviewing volunteers and members.  We wanted to know what CS meant to different people, and what role it had played in their lives.  Then we carefully read 1,000 member testimonials and 100,000 personal mission statements.  From this huge bank of information, we pulled out the words and concepts that seemed to be the most universal amongst CouchSurfers.

We found that while the words they used varied, CouchSurfers from all different backgrounds seemed to come back to a core group of concepts when talking about CS.  These concepts became the basis of our documents.

From there, it was on to a careful process of writing and rewriting.  Each time we developed a polished draft, we sent it out to CouchSurfers for comments and reactions.  With each successive round of testing, we re-evaluated our statements based on the feedback we’d received, and made changes as necessary.  With each new version, the number of members and volunteers who said that they “agreed” or “strongly agreed” with the statements grew.  By the time we reached the final versions, the percentage of those surveyed who fell in that category was approximately 90%.  Go check it out!

I’d like to thank all of the volunteers who worked on the development of these documents over the years.  I’d also like to thank the hundreds of CouchSurfers who sat for interviews, answered surveys, or provided feedback on drafts.  Without your help it would never have been possible to find common goals for our diverse community.  Thank you!

Sincerely,

Casey Fenton

CouchSurfing Founder

And it’s also understandable that a whole new generation of entrepreneurs are suddenly hot on bootstrapping, too. There are only two ways to start a business, after all: with capital or without. And in these uncertain times, capital is scarce.

via Start with Nothing, Planning and Strategy Article - Inc. Article.

If you run into trouble in a Mac with security_authtrampoline while installing Photoshop try:

sudo chmod 4777 /usr/libexec/security_authtrampoline

and let me know if it solved your problem

One reason programmers dislike meetings so much is that they’re on a different type of schedule from other people. Meetings cost them more.
There are two types of schedule, which I’ll call the manager’s schedule and the maker’s schedule. The manager’s schedule is for bosses. It’s embodied in the traditional appointment book, with each day cut into one hour intervals. You can block off several hours for a single task if you need to, but by default you change what you’re doing every hour.
When you use time that way, it’s merely a practical problem to meet with someone. Find an open slot in your schedule, book them, and you’re done.
Most powerful people are on the manager’s schedule. It’s the schedule of command. But there’s another way of using time that’s common among people who make things, like programmers and writers. They generally prefer to use time in units of half a day at least. You can’t write or program well in units of an hour. That’s barely enough time to get started.

via http://www.paulgraham.com/makersschedule.html

It’s been an exciting nine months since we launched the Google Chrome browser. Already, over 30 million people use it regularly. We designed Google Chrome for people who live on the web — searching for information, checking email, catching up on the news, shopping or just staying in touch with friends. However, the operating systems that browsers run on were designed in an era where there was no web. So today, we’re announcing a new project that’s a natural extension of Google Chrome — the Google Chrome Operating System. It’s our attempt to re-think what operating systems should be.

http://googleblog.blogspot.com/2009/07/introducing-google-chrome-os.html