161–170 of 229 posts
Earlier quoted context omitted.
Also imagine meeting your wife because you did a search query. Since we're in a purely hypothetical plane, both of these are equally plausible.
That doesn't make any intuitive sense. Meeting people starts with conversations.
By your logic, we'd literally be silent 99% of the time, because 'we have all the answers,' which is nonsense.
Earlier quoted context omitted.
Speaking as someone who writes blog posts littered with irrelevant pictures (but never on Medium!), I acknowledge your experience trying to solve a problem based on a blog post. Manpages and documentation are written to be references. Blog posts are written to be tutorials. They have different affordances, and as a result it is very hard to learn how to use something purely from a reference, and very different to sol…
There's one particular case where a look at a reference is warranted: when something doesn't behave as expected. For example, the other day someone asked on stackoverflow why a particular Java class to calculate a difference between two dates was returning a weird result when they asked for the difference in days. Turns out, the class would calculate the difference in years AND months AND days, so if you asked for th…
The other problem is that you're not really fighting JS or CSS or HTML per se, but a browser implementation of interpreters for that. And you don't really have a say in the matter, because you're not picking what browsers are using your webapp, your users are. This is only really solvable using a combination of MDN, Stack Overflow, and Google-fu.
I'm a middleware support engineer. A reasonable amount of experience, coupled with Google, will solve many problems.
Google is not a search engine. It is a memory upgrade, and anybody who tries to write software with a standard human memory is obsolete.
So many people missed the point of this post that I ended up replying to it instead of them. "Memory upgrade" means not relying entirely on your own memory and previous knowledge. That doesn't exclude internalizing the language, nor coming up with new solutions. It probably changes a lot depending on what you do, but I've found it imperative to keep up to date with an ever-changing engine, and it would have been malp…
Anytime I learn something new, I create a simple project using that new thing as a way to memorize it better but also be able after few years revisit it and either remind myself about it or improve it.
So one of the things that the author should Google is “salesmanship“. Everybody uses Google as a reference, no shame in that. Everyone uses spell check also. But would you go into an interview and proclaim your a lousy typist dependent on spellcheck? Putting your full real name on a blog and announcing to the world that your a lousy developer, that is just as bad. Much like cops posting racists rants, people on disab…
The interviewer who expects me to have every little detail about every single technology I've used in the past stacked up in my mind, won't be worth my time, not to mention joining their company. The comparison to spelling prowess is apples and...melons. Use your favorite search engine to look up "what is the difference between insight and information?"
Using search engines sometimes feel like a lost art if you spend any time in Facebook groups, where people will ask mundande, simple, and easily Googleable questions. Sometimes I wonder if people do it to fill some sort of social need, and don't particularly care for the answer.
Every Google search you do is a lost opportunity for an unexpected conversation. Imagine never meeting a wife because you did a Google search instead.
Earlier quoted context omitted.
> One of the things I don't like about webdev (among many) is that I even have to Google in the first place. Manpages are so much more immediate and accessible. I don't really get this response. First there's the notion that "webdev" is the discipline where information is so fractured that you need to go googling around to figure out how to do everything. All the other disciplines have a magic thing called a man page…
Also the "manpage" does exist - it's the spec. But I've never met a single person who has ever directly read it.
A big part of it is that imho technology has gotten more powerful, but still no easy to use. Like, I'm imagining in 20 years the API for Amazon's drone fleet will be here and we'll still be like "wait, the address parameter is for an IP address? And the library isn't thread-safe but also doesn't connection pool so I have to maintain one dronecloud client per thread? And what's this cryptic "rotor invert" error? It fe…
Earlier quoted context omitted.
Wrong. Software is not so complicated that you have to Google search everything every time. If you are not internalizing new knowledge, you are performing poorly.
> Software is not so complicated What kind of software do you write? Software is one of the most unnecessary complex things humanity has invented.
Earlier quoted context omitted.
> One of the things I don't like about webdev (among many) is that I even have to Google in the first place. Manpages are so much more immediate and accessible. I don't really get this response. First there's the notion that "webdev" is the discipline where information is so fractured that you need to go googling around to figure out how to do everything. All the other disciplines have a magic thing called a man page…
Also the "manpage" does exist - it's the spec. But I've never met a single person who has ever directly read it.