212 karma · joined March 27, 2013
It's a dilemma, as Java+XML is very verbose. still, with the amount of work Android Studio does, I'm not sure its a big problem for most of us Android Developers.
...if this is a fox luring me into it's hen-house, the hen-house sure is comfy and well-featured. Sad to see it diminished in this article, when IMO it's a far far better offering than any other major companies (looking at you Facebook) are putting out.
7. Don't disappear from the retail chains. Rent space in a computer store, flood it with Apple products (especially software), staff it with Apple salespeople, and display everything like you're a living, breathing company and not a remote, dusty concept.
More expensive, but worth it.
Edit: also, I like the Stevia soda, but no-calorie sweeteners always leave an acrid taste in my mouth, and upset my stomach so I prefer Dry Soda or just plain seltzer water.
Also, I've had a similar experience running Visual Studio + SQL Server.
For the most part, the portable computer is a dream machine for the few.
that really miss.
And then their is the conclusion, which comes after the author acknowledges the possibility of improvements in laptops.
But the real future of the laptop computer will remain in the specialized niche markets. Because no matter how inexpensive the machines become, and no matter how sophisticated their software, I still can't imagine the average user taking one along when going fishing.
What?! To me that just shows the author downplaying the idea of the technology. He just couldn't imagine any laptop ever being more than a "niche".
The article starts off describing laptops on airplanes, the tag about fishing just seems like an exaggeration by the author. I would say that the author was wrong and this is a good example of a bad prediction. I mean, did you read the line about floppy disks? The authors points were that laptops are #1 to heavy #2 their software doesn't stack up and #3 their price is far to high.
All of the predictions are wrong, so I see this author as betting on the wrong horse.
This should not be conflated with hacking though and software development. You can do both of those without any strong background in mathematics. Alot of software development and hacking is just using things people with CS skills built. I do not have to understand quicksort to use the native library sort.
Uber has customers, real revenue (in the billions). So does AirBnb. So does SpaceX. So does Palantir.
Just name dropping WhatsApp is pretty low brow. There are alot of people doing incredible things (Sam's point I might add) and focusing on the Bubble makes you miss out on companies generating real revenues.
I love algorithms, AND I think they are necessary in interviews, but I feel like the tech community has become ridiculous in how they interview for them lately.
Example problem: Given two words in a dictionary, transform one word into another, changing one character at a time, using only words in the dictionary.
A good interview would recognize most people have no clue how to solve this, give hints and still pass candidates who make a reasonable attempt but fail. Now it seems to be that most places will just fail you, if you don't know the most optimal answer and can't write it out without any syntax mistakes.
This is ridiculous, and I have experienced it and this attitude around major tech companies. What this has resulted in is Algorithm trivia. Your ability to succeed is your ability to memorize every algorithm question and approach in existence.
For example, I remember one developer (who know works at Amazon funny enough), who used dual for loops to iterate through data and find values in multiple places in our application. This caused a noticeable UI slow down. I ended up just loading this data in a Hashmap and it became instantaneous.
With consulting, you are not necessarily responsible for execution. Your job is primarily to make recommendations. That said, much of my consulting work has also been comprised of executing on my recommendations.
With freelancing, the work tends to be either in reality consulting or in most scenarios executing on a spec, or under another developer's guidance.
If I were to put it simply, consulting stems from offering recommendations and direction from a place of knowledge and experience related to your skillset, whereas freelancing tends to be more the application of your skillset.