https://medium.com/@loorinm/becoming-a-software-engineer-is-... She was admitted to "Hack Reactor" in October 2015. Well that escalated quickly.
317 karma · joined March 18, 2016
https://medium.com/@loorinm/becoming-a-software-engineer-is-... She was admitted to "Hack Reactor" in October 2015. Well that escalated quickly.
Javascript was only created to make web pages more dynamic when web pages, and nothing more. Back then browser was supposed to be just a "thin client" to access everything magically and only way to keep things locally on the browser was through cookies.
That's not the case anymore and web browsers became a monstrous software that does everything, and that's why we're even talking about "libraries".
Also you say "JS continues to make poor excuses as to why it continues to not have one", but that's exactly what the ES6 is trying to do, with classes, inheritance, etc. I personally do not like that direction, but hope that makes you happy.
Like you said it was never designed to have a standard library and so forth, and therefore it sucks to use JS to do a lot of things.
However I was just saying I don't think it's fair to say something is badly designed because it's bad at doing things it wasn't designed to do. The interpretation of whether having a functional scope is good or bad is also subjective IMO, depending on context.
But anyway if your takeaway from my comment was just this, you didn't get my real point at all. I don't really care about whether javascript is a good language or bad language. My real point was this whole disaster is caused not just by javascript alone.
I don't think Javascript is a bad language. It does what it does and is good enough.
In my opinion if you look at where Java is right now, that's where javascript is heading towards--it's madness and an epitome of extreme bureaucracy--and it's not because Javascript is a bad language, you can't really pinpoint what exactly caused this because there are so many factors. Node.js is not even the core reason. It's actually HTML5.
HTML5 allowed for all kinds of new features such as localstorage. There used to be times when only way of storing things locally was through cookies which was limited to 4KB. With that spec, all the modern frontend web technology wouldn't have been possible. This includes really anything that gained traction in recent years such as Backbone.js, React.js, etc.
Anyway my point is, it really sucks where this is all headed. Especially looking at javascript itself evolving to become needlessly complex. What we're seeing is just tip of the iceberg, i presume it will get much worse once ES6 actually becomes the functioning standard across all browsers.
People should focus on building meaningful stuff, nowadays what I see is bunch of people boasting how they're a great "frontend developer" by knowing some new build tool or frontend js framework or css framework, which probably will become obsolete in a year or so (Hello grunt, hello backbone).
Just three years ago to build a website all I needed was js, css, html, and maybe some jQuery. Nowadays I need to write coffeescript or es2016(why do they even need to name it that way I don't know), which compiles to JS, write Sass or Less that compiles to CSS, use handlebars for templating which compiles to html, and package them altogether using Grunt, Gulp, or Webpack. When I make a line change, I used to be able to immediately refresh the page, now I need to wait until grunt autodetects the file change, compiles each coffeescript, compiles each template, compiles each stylesheet, and finally reload.
Sometimes I go on a no-carb diet (sometimes to lose weight and sometimes because carbs make me sleepy) and I am too lazy to buy ingredients and cook at home.
I just want soylent, but with 0 carbs. Anyone know?
You should always under-promise and over-deliver. It's kind of a bummer to see a customer support app since I was expecting a groundbreaking technology that finally succeeded in implementing teleportation technology using gravity distortion
When talking about these things you should keep in mind whatever you say is just an opinion and a theory. Just like Newton's law was the reality until Einstein came along, the "reality" is nothing more than our interpretation of the world.
That's why I think it's not a good idea to conclude someone is "wrong" for technical reasons. Our "technical" reality has been evolving and will keep evolving, so our reality today won't be the same as tomorrow's reality.
I have no problem someone saying "it is very likely we live in a simulation" because it's an opinion and he's not trying to hide the fact that it's just an opinion.
But saying stuff like "THAT IS WRONG" and "It's conceptually and empirically incorrect" is really amateur.
By the way does this guy even know what "empirically" means? Our experience is nothing more than what we perceive as human beings, and there's plenty of evidence that supports that what we perceive is not necessarily the reality. And this guy is saying "it's empirically wrong". It is impossible to prove a philosophical theory "empirically wrong".
Like I said it only makes sense when you feel the need to make it open source. Some of the reasons I could think of:
1. Your app has features that are very privacy sensitive, so you want to let your users know there's nothing fishy going on. 2. You're not building the app because you want users, but as a learning experience. Hey maybe you can even use your public code as your resume (Then again, this can backfire if your code is not exquisite) 3. Marketing stunt (This won't work in most cases, so if you're thinking of this don't do it) 4. Your app has server aspect and you can't afford to run it anymore so thinking of shutting it down, but you want to do your users a favor.
Community involvement and participation will NOT come just because you open sourced it. In fact you should assume it won't happen. This is true for even extremely successful open source projects. It's only less than 1% of people who contribute and 99% of freeloaders.
The whole point of this discussion thread is that Imgur is f*ed because they aren't independent enough. Otherwise there's nothing to worry about, right?
Summary: userbase/community was what drove the network effect, which made it impossible for Google to catch up, and that's why Google made the decision to purchase Youtube.
Just my personal opinion: users don't care if your app is open sourced or not (Unless there's a clear reason for it to be open sourced, for example providing transparency in cases user privacy is critical)
Non-monopoly is a commodity.
Imgur is just a commodity. Youtube is not.
We have no idea how brain works, so we can only make hypotheses based on experience. When someone can "see" an answer without being able to explain how he came up with that answer, regardless of how useful that skill is in the real world, that is something. Maybe sometimes all his neurons connect instantly in certain circumstances. Who knows.
Another reason I think this is possible is because sometimes I come off that way (to much lesser degree) to other people. Sometimes when I come up with a solution to a problem (not at all domain specific), people wonder how I can do that. I can't explain of course. I am not trying to say I'm a genius. I'm saying things like this happen sometimes for no reason. And "highly intelligent" people tend to have more of these than "normal" people.
Anyway, these are all just theories, yours included. So I think just saying that our brains objectively work in certain ways is not a good idea, and is probably wrong.
If we're talking about the ideal world that may be true, but the real world is far from perfect. If you ask 100 people do you want to live a meaningful life, probably 99 of them will say yes. But do they? Probably 1 out of those 100 will live a meaningful life. If you ask people do you want to be told what to do, or do you want to do what you want, most of them will say they want to do what they want. But in reality most people just want to be told what to do because making decisions and being responsible for it is not an easy thing.
Coming back to Facebook feed, there's a reason why people keep using Facebook even though many people hate it. Sure it's not ideal but there will never be an ideal world. I think the reason why most "decentralization" advocates never succeed is exactly because they're being too ideal (read naive) about this.
That said I think the pendulum will swing back someday in the future surely, it just won't be by these guys. It will be from some random technology which didn't even aspire to "disrupt" the web.
"Leaving it off the resume" means lying, and they will most likely ask what happened during that time. Even if they don't ask it's a bad sign since it means you come off as someone who's been unable to get a job for whichever duration you worked on your startup for.
From my experience companies only look at your objective skills when they hire you. And a lot of large companies actually respect that you have worked on your own company even if it failed.
So don't worry about what it means, if you're trying to find a job, study for the interview really. That's one thing I messed up when I shut down my company and had to get a job for the first time in my life. I didn't even know "preparing for an interview" was a thing and failed miserably at some of the early interviews I did, but later figured out there's a formula and then I aced everything, ended up getting multiple job offers and chose the one I wanted.