enrmarc's comments

Reading "Cracking the coding interview" is like studying the day before of an exam.

In Germany I'd say Cologne.

I did it two years ago. No regrets so far.

I read the paper, but I did not understand a thing. What is the path to follow (for example, books or papers to read) in order to at least understand what the paper is talking about? My background is in computer science.

Capsule Corporation (from Dragon Ball): "a company that creates special small capsules that shrink and hold objects of various sizes for easy storage".

Off-topic: do you know if there exist glasses that do not touch the nose?

Vue.js

Last time I read about age discrimination in software development, 40 (years) was the number. Now it seems it's 30. In 5 years I suspect that anyone above 25 will be considered "too old" for this profession.

Not so crazy if you think about it: right now, 30-year-old people have about 8 years of experience (assuming a 4-year degree) and, as this post suggests, are being discriminated. Now, imagine an 18-year-old guy that study a year (code camps?) to become a software developer and after that starts to work as one. At 25 he would have 6 years of real world experience (let's assume this guy likes the profession so he taught himself while working, in order to compare both developers). Who has more chance to be hired (under the assumption that age discrimination is still a thing in 2021)? 2 more years of experience doesn't seem too much and a 25-year-old guy seems to be more suitable to be tricked into working 60 hours a week for less money.

Update: grammar fix.

I do it every day, although my background in maths/physics is not enough to do it "the scientific way". There is one topic I'm constantly thinking about: "Where is the data, e.g. the mass of a planet, stored in our universe?".

I guess this question arise because of my computer science background (algorithms + data = universe?) and because even simple formulas like the Newton's Law of Universal Gravitation deals with data (e.g. the mass of a planet). So, where is that number stored so the universe know how to apply its formulas (laws, algorithms)? I know these laws we have are just models of our reality that are getting more precise over time, but I can't help but think that at the end our universe has to do "some calculations" and has to deal with data (numbers). I know three devices that can store information: our brains, our DNA, and our computers. The color of our eyes are stored in our DNA, but the mass of a planet is not stored anywhere?

As I've said, my limited maths/physics background doesn't let me think about the universe the right way. I'm just a dilettante. And sorry for my English.

Couldn't we say the same thing about Ruby?

Why does Python use methods for some functionality (e.g. list.index()) but functions for other (e.g. len(list))?

http://effbot.org/pyfaq/why-does-python-use-methods-for-some...

I guess is that.

IMHO Ruby is a good candidate.

> So when you change job of your own initiative, it is assumed that you first get a new position, then give a notice and start your new position.

It's pretty much the same in Europe (except when you take gaps, of course).

> I'm not saying it's right or wrong; just explaining how long and recurrent gaps can be interpreted.

Recurrent gaps can be interpreted in a lot of different ways, but there is just one real reason behind them. But I see how recruiters can assume things before asking for real answers (e.g. 6 months gap and this guy hasn't been able to find a job? Next!). It's a pity.

Serious question: what's the problem with résumé gaps? Is it a big deal in USA? I'd say that in Europe it's not such a big deal. Nobody is going to ask you why you have, for instance, a 4 month gap in your résumé if you have been working 3 or 4 years in a row. Almost everyone would guess that you took that time off, and that's not a bad thing precisely. Perhaps you took that time to learn new skills, to read a ton of books, to travel around the world, to be with your kids,... a lot of activities that do more good than harm. Most of us are going to work until we are 60 or so, so what's the big deal with having a few months every 5 years or so in our résumé? They give you a medal if you finish your career without gaps?

Imagine this scenario: developer A has been working in a time span of 10 years without résumé gaps. Developer B has been working for 9 years and has been taking gaps of 4 months every 3 years. Do you really think there is going to be a big difference between the two developers in terms of skills set? 10, 9, 8 years, it doesn't make a difference at all in terms of accumulated knowledge. But developer B has been doing "something else" during a whole year (3 gaps of 4months each). Maybe he travelled the world and learned a little bit of a couple of languages, and I'd say that's a valuable non-technical skill to have.

As I've said, I see more good than harm in taking a few month off from time to time.

Going back to your question: if it's just for a few months I see no problem at all, and if recruiters ask then just explain what you have post.

Really interesting!

Offtopic: I like the syntax themes. Something similar for Atom?. Specially the third one from the left https://d2f7qn9vg9vryy.cloudfront.net/site/syntax-themes.png

I use WebStorm at work.

Atom for personal projects.

GVim when I have to write something down.

That's something I did/do with English. I usually listen to podcasts while going to work (about 1h commute) and it's kinda difficult sometimes to "hear" what it's playing. I mean, I get distracted and suddenly I have no idea what the podcast is about. But I guess that's part of the "passive" exposure.

I forgot to mention apps! Yes, Duolingo is in my list.

Offtopic: how did he turn the README.rst into a webpage?