lang:en - Sarah HL on Diigo

20 Nov 09

In this post, I'd like to share a bit on what our recruitment process looks like, what we look for in people and what working at Ibuildings means for our staff
We like to believe that we have great positions for developers.
19 more annotations...
- Solving the functional requirements of a project is one thing, but making sure that it still works when 11 million people visit the site on a single day is another!
- it has to do with the fact that many of our developers do not regard their work as 'just a job'
- They are motivated and eager to build cool stuff.
- learn while they work
- Though experience is important, there are many other things we pay attention to, such as software engineering skills (development is more than just coding)
- 1. Screening your CV
- we'll ask you to fill out a self evaluation. This gives you the ability to tell us how much experience you have with certain topics and how you would rate your own skills
- 2. A self evaluation
- 3. A coding test
- with 10 years of recruiting experience, it works for us and it works well
- it’s really to see a developer in action
- 4. An interview with an Ibuildings manager
- we get to know you and talk about your ambitions, what you look for in a career
- 5. An interview with one or two software engineers
- your potential future co-workers
- they will also identify the areas where we might need to train you (we can't expect everybody to know everything, of course)
- 6. Reference check
- if you've done community work or built open source applications, those are interesting references as well
- 7. If we believe in you, and you believe in us, then we offer you a job

Encouraged Commentary | DontTrustThisGuy.com

donttrustthisguy.com/...encouraged-commentary - Preview

mediassociaux lang:en tips

09 Nov 09

Marissa Mayer: The Visionary: Women of the Year: glamour.com

www.glamour.com/...marissa-mayer - Preview

google féminisme lang:en

Marissa Mayer
“I do code all night! I am the stereotype, but I also break the stereotype.”

06 Nov 09

Gallery | Mission Bicycle Company

www.missionbicycle.com/gallery - Preview

vélo lang:en mediassociaux

04 Nov 09

Why Your Friends Have More Friends Than You Do | Psychology Today

www.psychologytoday.com/...iends-have-more-friends-you-do - Preview

psychology lang:en

27 Oct 09

Interoperability Principles

www.microsoft.com/...default.mspx - Preview

formatsouverts lang:en microsoft

26 Oct 09

10 principles of design - Dieter Rams

www.tendesignprinciples.com - Preview

design tips lang:en

03 Sep 09

How to create your personal manifesto

www.gwenbell.com/...e-your-personal-manifesto.html - Preview

lifehacks gtd geek lang:en tips inspiration

I am a fan of the physical act of writing before committing goals to the digital medium.
Vision Map
16 more annotations...
- 1. Gather the necessary supplies. Magazines of all genres, glue, markers, pens, cardboard in all sizes, scissors, water, music, snacks
- Share with the group what you've created.
- add a photo of yourself to the map - will help you really visual yourself living this life
- Life List
- Ask someone about their dream today, she suggests. I'm with her.
- Digitized Goals
- I completed the Lululemon Goaltender process. If you are a completely digital type, this might be the best route for you.
- They print it on their bags and have them available in poster size at their stores free of charge.
  
  Microactions
- Once you're clear on vision, microactions
- become much easier to complete
- Beware, OPDs. Other People's Dreams.
- I am all for helping others. I am all for engaging in other people's projects - with awareness. But I think there's a danger in (myself and many of my helper-type peers) becoming so consumed with someone else's dream that we forget to pursue our own. That's one reason you may benefit from doing this sort of work twice a year at least.
- Minimize Distractions
- Creativity v Productivity
- Resources aka The Well of Well-being
- Sabrina Ward Harrison: Spilling Open
  
  Sark: Micromovements
  
  Barbara Sher: Refuse to Choose (one suggestion she makes, if you think you want to do everything is to make a list of things you definitely do not want to do)
  
  Merlin Mann: 43 Folders specifically, his post on the problem with productivity pr0n
  
  David Allen: Getting Things Done
  
  Chris Guillebeau: You know you want to see the world, Chris shows you how
  
  Leo Babauta: Zen Habits
  
  Danielle LaPorte: White Hot Truth
  
  Jen Lemen: Get your heart all warmed up
  
  Julie & Julia: Watch it if you're needing a creative boost
  
  Andrea Scher: For days when nothing else works, wear a Superhero Necklace. Elevate yourself.

12 Aug 09

PHPCamp: learn something new everyday

phpcamp.net/index.php - Preview

php articles lang:en

29 Jul 09

Dotjay’s Lab | dotjay.co.uk

lab.dotjay.co.uk - Preview

usability links lang:en

Symfony deployment Cheat Sheet

symfony-check.org - Preview

php programming webmastering lang:en symfony

13 Jul 09

How to Use PHP Namespaces, Part 1: The Basics

twittexperts.com/90907581326 - Preview

php programming opensource lang:en

02 Jul 09

The Pomodoro Technique

www.pomodorotechnique.com - Preview

lifehacks gtd tech lang:en

ongoing · Test-Driven Heresy

www.tbray.org/...TDD-Heresy - Preview

programming tests test_driven testing lang:en

As a profession, we do a lot more software maintenance than
we do greenfield development.
39 more annotations...
- we do way more maintenance than initial development. And in my
  experience, the first-cut release of any nontrivial software is
  pretty well crap.
- But to do that well, you absolutely must have enough test coverage
  that you just aren’t afraid to rip your code’s guts out
- I always end up sketching in a few
  classes and then tearing them up and re-sketching, and after a few iterations
  I’m starting to have a feeling for X and Y.
- I freely admit that this is not really truly TDD
- once you’re into maintenance mode, there are really no
  excuses. Because you really know what all your X’s and Y’s are
- Writing the tests points out all the mistakes you might make in signatures, prerequisites, etc. If the tests are too hard to make then you know that your API will be too hard to use, you're doing it completely wrong, and may as well pause for a rethink.
- While the approach you advocate makes sense, it does require professionalism, not just from the developer but from management too.
- the person left to maintain the code isn't the person who wrote it, leaving the maintainer with an unholy mess to untangle. Getting unit tests into such code is a monumental task.
- he failure to address how unit tests can be introduced to an existing non unit-test codebase. (i.e. go from non-TDD to TDD)
- I feel the TDD community only wants to focus on greenfield projects and has ignored maintenance/legacy issues. Which is strange when as you say code spends most of it's time in maintenance
- The thing is that as long as the project is small you really don't see the benefits of TDD. I've done a couple of small projects and never had to go back to them ever again
- Never use mocks unless you are mocking an interface that will almost never change
- You are writing the client code (in the form of a test) so you are thinking how the worker code will be used. What is its public interface and what do you want it to do when it's called
- From: Tathagata Chakraborty (Jun 24 2009, at 07:31)
  TDD is useful in another situation - in a commercial setting and when detailed specification documents have already been created by say a technical expert/architect. In this case you don't have to do a lot of designing while coding, so you can start off with the test cases.
- writing the tests *first* is that it helps keep your code focused on exactly what it's meant to do, and no more
- When work on production code begins, most of the code should fall into the categories of things that are not to be tested.
- In theory, TDD is a great idea. The problem with TDD can be expressed in one word: money.
- One approach to the unknown X and Y problem that I've been using recently has been to pretend that class X has been written already, and then write code that uses this pretend X object/API. I usually write this directly in the file that will become my unit test. Since X doesn't exist, I'm allowed to call whatever methods I want and pretend it all works. Once I'm satisfied with how it all looks, I cut and paste everything into a bunch of failing tests.
- I get really bored adding tests to code that already runs
- religious zealots
- the seductive TDD trap
- There is nothing wrong with building tests after you have built your product.
- that goes a long way towards taking software development from a form of artisanal craftsmanship to a real engineering profession.
- using tests to drive development cripples innovation, dramatically slows development
- It always seem to me to be a codified form of reverse engineering, or at least a way to force the programmers into looking at their code from two separate angles at the same time.
- If you're just adding tests at the end, then it's normal unit-testing, isn't it?
  - The point :) - on 2009-07-02
  Add Sticky Note
- I do realize that this type of exercise might help younger coders in getting better structure, they do often rush in too quickly and focus more on the instructions than the abstractions.
- TDD is test-driven *design*
- He said he didn't write tests in cases where it would have taken him several hours to get a working test for a small piece of code.
- In some applications, objects are self-contained, activities are sequential, and algorithms are tricky
- I've seen cases where people have wrecked the architecture of systems in the name of making them testable... But have never written the tests.
- Yes, it's possible to make peace with testability, and in the best situation, testability can improve the architecture of a program, but it can also lead people away from highly reliable and maintainable KISS approaches.
- Like any infrastructure, it is always beneficial to provide unit testing. The most benefit is derived from installing it as early on in the project as possible.
- The value of an untested feature, to a client, is ... zero. So, it doesn't matter how many of these you have rattled off in the past week, your net throughput is effectively... zero."
  - testable == Measurable - on 2009-07-02
  Add Sticky Note
- You can see in this thread the word "professionalism" (substitute "morality" with little gain/loss of substance) and even "sin" (used in jest, but not really!)
- if I delay writing unit tests until after all the units are working together then because the system "already works" my subconscious enthusiasm for writing unit tests falls markedly, and so their quality and coverage fall
- Experience teaches that if I generate that output by hand (1) it takes *much* longer (2) I almost always get it wrong. So I often write the code, get its output, carefully check it (really...) and then use it as the correct result.
- My main objections to TDD are: 1) it promotes micro-design over macro-design and 2) it's hard to apply in practice (i.e. for any code that is not a bowling card calculator or a stack).
- the tests are just a persistent artifact of the exploratory coding I've already done.

01 Jul 09

phptwitterbot - Google Code

code.google.com/...browse - Preview

twitter lang:en programming php

30 Jun 09

Subversion Best Practices

svn.collab.net/...svn-best-practices.html - Preview

bestpractices lang:en tools tuto

Communications | Open Source Alternative - osalt.com

www.osalt.com/communications - Preview

opensource lang:en tools

Top 10 Responses to Why Should I Use Linux? - A Linux Evangelists’ Reference » Linux, open source and me at Internetling dot com

www.internetling.com/...-a-linux-evangelists-reference - Preview

opensource linux lang:en

1. Linux helps you get rid of viruses, worms, and other computer infections.
2. Linux is fast and will stay fast
8 more annotations...
- 3. Linux is easier to use than Windows. Using the Terminal is not necessary in most cases.
- 4. Linux is free as in free beer
- 5. Your porn collection is safe with Linux
- 6. Thousands of Windows-only applications (even Photoshop CS3) and games work with Linux through WINE just as fast. You can also find good alternative open source software.
- 7. Linux looks better than Windows Vista or Mac OS X
- 8. Linux is fun
  
  People always tell me this. And why? Linux users have the power to expand their system for free, they are free to modify the system exactly to their needs.
- 9. You can help improve Linux
- 10. Linux makes you give your computer a name

40 Essential iPhone Applications For Web Designers

www.sitepoint.com/...one-applications-for-designers - Preview

iphone programming webmastering lang:en pourSesLiens

29 Jun 09

How to Listen to the User and Hear the Experience « Usability Post

www.usabilitypost.com/...how-to-listen - Preview

formation lang:en tips

Sarah HL's Library tagged lang:en → View Popular

Ibuildings - Blog - ibuildings.co.uk

Encouraged Commentary | DontTrustThisGuy.com

Marissa Mayer: The Visionary: Women of the Year: glamour.com

Gallery | Mission Bicycle Company

Why Your Friends Have More Friends Than You Do | Psychology Today

Interoperability Principles

10 principles of design - Dieter Rams

How to create your personal manifesto

PHPCamp: learn something new everyday

Dotjay’s Lab | dotjay.co.uk

Symfony deployment Cheat Sheet

How to Use PHP Namespaces, Part 1: The Basics

The Pomodoro Technique

ongoing · Test-Driven Heresy

phptwitterbot - Google Code

Subversion Best Practices

Communications | Open Source Alternative - osalt.com

Top 10 Responses to Why Should I Use Linux? - A Linux Evangelists’ Reference » Linux, open source and me at Internetling dot com

40 Essential iPhone Applications For Web Designers

How to Listen to the User and Hear the Experience « Usability Post

Selected Tags

Related Tags

Sponsored Links

Top Contributors

Groups interested in lang:en

PHP Programming

Web2.0

Tools for web developers