aercolino

Don't. Just leave. To each, their own mess.

Oops, I expected funny jokes, I got depressing facts.

At a ticketing company in Barcelona, Spain, now working on a web interface to automate graphical assets creation and deployment.

Yes, spaghetti-code is much better! /s

> Following the logic

That's what names are for. I prefer to find _afterLeft_ spread all over the place rather than `x2<=x1` even if it actually increases code size by 50%. I can validate it only once, and if I stumble upon _aboveBottom_ I don't even need to validate it to infer what it means (left as an exercise for the reader).

This spaghetti line: `x2<=x1&&x1+w1<=x2+w2&&y2<=y1&&y1+h1<=y2+h2`, in my opinion, is much harder than `inside`.

I stopped reading before finishing the third page. It seems to me that what many paragraphs advise is to be reasonable, which is meaningful, but a bit too loose for guiding code reviews.

META

May I ask you to change the leading text to something more useful for remote workers?

REMOTE doesn't cover but the most basic possibility and 90 matches on this page make it quite cumbersome to find what suits you.

What about deprecating it and requiring posters to use instead:

REMOTE_WORLD - for telecommuting from anywhere in the world

REMOTE_US - for telecommuting from anywhere in the USA

REMOTE_US_TX - for telecommuting from anywhere in Texas, USA

REMOTE_MINUS_6 - for telecommuting from anywhere in the UTC-6 timezone, standard time

REMOTE_PLUS_1 - for telecommuting from anywhere in the UTC+1 timezone, standard time

Example: In the past, I telecommuted to Boston (US-MA) from Barcelona (ES). That job would have been advertised as "REMOTE_MINUS_5, REMOTE_WORLD". In fact I worked 3pm-11pm in ES (i.e. 9am-5pm in US-MA), which was certainly unusual but quite doable nonetheless.

I find it difficult no to love this young girl.

Clearly not the kind of women we need more in tech... well, we don't need fanatics anywhere really.

The PDF document lacks the last endnotes. 189 is the last one on page 28, but the endnotes list stops in the middle of 167.

I would live in a big city with plenty of opportunities. Find an interesting job, where to work no more than 20 hours a week, and earn around 60K. I think your Angular experience is very marketable. And you can always tell your prospective employers the truth, that you made an application too good to keep working there for maintaining it at your salary level. Then use your free time for whatever you want, including meeting lots of people. You could find cofounders...

It's funny to see how many comments advise about beginning a Start Up. Of course, this is a Start Up forum. If this was a farmers forum, would many advise about beginning a farm?

Very. Well. Said.

Sorry to add a critic. If you want to make your PHP classes easy to extend, refrain from private and prefer protected. Otherwise, a developer that wants to extend one of your classes will need to also override (i.e. copy and paste) into her class all private members called from the members she really wants to override.

If you want to see how they code, why do you want to see their own algorithm? In normal conditions, They would Google the problem and find its algorithm on Wikipedia (with lots of additional information to peruse) and some interesting implementations on stackoverflow (both to choose from and to learn about related issues).

Programming in the wild has very little to do with knowing beforehand or being able to invent on the spot an algorithm.

But the real reason why software engineering interviews are being done that way is because programming is not perceived as an art anymore. Engineers' scope inside the company was greatly reduced, while their number increased. They are now commodity workers: Not only they must be replaceable, but also expanded and shrunk as soon as possible, much faster and cheaper than before.