A Rocket Internet experience @ ForumPHP Paris 2013

A ROCKET INTERNET
EXPERIENCE

Alessandro Nadalin, 22nd November 2013

AGENDA
1. Context
2. Responsibilities
3. Building the team
4. Get started
5. Mutate
6. Delegate
7. BONUS

You can't make everyone you know relocate

You can't relocate your company

How to hire a very good (middle-eastern) team?

They forget about the clock and are
usually attracted to new technologies

Moreover, there is no big bias.

How many PHP indians companies are out there?

No one expects everyone to know about everything,
that is why we hire people and train them

Training has a cost that both the employer
and the employee have to split

Means overtime for
changing labels it's useless,
of course

It's a matter of what both parts
offer for / in those extra-hours.

What is the second-system effect?

Why is OOP better than procedural code?

What happens when you hit enter in the browser bar?

An interview is always a good opportunity for
learning.
Given that you can effectively teach stuff with
the pyramid interview...

...ask how many cabs are out there if you want.

If you ask weird questions...

Putting the candidate in a no-comfort zone will
let you know how he or she reacts to variable
situations and unknown problems.

If you wear shorts...

Gain authority on the field, not on paper


Gain authority on the field, not on paper
Remember people not to be judgemental


Beach after Work!

A Rocket Internet experience @ ForumPHP Paris 2013

"It takes 3 months to be effectively productive"

"Because the developers can't understand the code"

Why don't they understand the code?

"Because the code is not that domain driven"

Solution #2
Replace the software

In the next 4 months, we would have replaced our
entire architecture with a RoR application and parts
of the architecture with NodeJS...

Know-how and tools for free is something you can't
easily drop.
Instead of replacing a monolithic approach with
another monolithic approach, you split the system
in layers and work on each of those layers.

So, why isn't the code domain-driven?

"Not everyone knows how decoupled DDD works"

Imagine Fabien as your boss
when you were a Rookie?

Socratic approach
Question something

Socratic approach
Question something
Raise your thoughts

Socratic approach
Question something
Raise your thoughts
Let them elaborate

Socratic approach
Question something
Raise your thoughts
Let them elaborate
Drown together

Socratic approach
Question something
Raise your thoughts
Let them elaborate
Drown together
Accept evidences

Socratic approach
Question something
Raise your thoughts
Let them elaborate
Drown together
Accept evidences
Ready to move on

Do not change people because
you want things to get better.
Change things because
you want people to feel better.

All of this besides day-to-day development

~3 months: 1 deployment a week

~9 months: 2/3 deployment a week

~1 year: ½ deployments per week

~1.5 years: whenever s**t is ready

"Instead of replacing a monolithic approach with
another monolithic approach, you split the system in
layers and work on each of those layers."

A software design based on discrete software
components, "services", that collectively
provide the functionalities of the larger
software application

You typically start with the
infamous web application
which does everything on its own

Then you realize that to provide
a chat system to your users
PHP might not be the best...

And soon you also decide,
to improve performances,
that your frontend should have its own
in-memory persistence, to be faster
and you put it into another service

And eventually, your lead architect
will come up and tell you
that your Java-based chat
sucks and should be
replaced with...

In human-understandable words, SOA is a software design which
embraces splitting a monolithic, totalitarian software
architecture into smaller pieces, thus making them independent,
loosely coupled and more maintainable

...and a new frontend pops out

Another one might want to deal
with the same data...

And ask the first one to compute some data...

And once it's done, there might be the chance
we want to raise an event...

And monitor if there is a problem...

No one is designing Web Services for you anymore

Don’t limit yourself to develop stuff

Release management
http://odino.org/source-code-workflow-after-3-months-of-github/

Alessandro Nadalin
@_odino_
Namshi | Rocket Internet

Alessandro Nadalin
@_odino_
VP Technology

Alessandro Nadalin
@_odino_
VP Technology
odino.org

Thanks!
Alessandro Nadalin
@_odino_
VP Technology
odino.org

namshi.com/careers/
http://www.youtube.com/watch?v=NThxiu1HGgM

A Rocket Internet experience @ ForumPHP Paris 2013

A Rocket Internet experience @ ForumPHP Paris 2013

Recommended

More Related Content

Similar to A Rocket Internet experience @ ForumPHP Paris 2013

Similar to A Rocket Internet experience @ ForumPHP Paris 2013(20)

More from Alessandro Nadalin

More from Alessandro Nadalin(20)

Recently uploaded

Recently uploaded(20)

A Rocket Internet experience @ ForumPHP Paris 2013