JSDave

"Artificial general intelligence (AGI) is a type of artificial intelligence that matches or surpasses human capabilities across virtually all cognitive tasks."

AGI is when it can do all intellectual work that can be done by humans. It can improve its own intelligence and create a feedback loop because it is as smart as the humans who created it.

Instead of generating, exporting or copy pasting just seems more reliable to me and also takes very little time.

I think what matters most is just what you're working on. It's great for crud or working with public APIs with lots of examples.

For everything else, AI has been a net loss for me.

My point is that people making 200k-1000k are closer to middle class than billionaires. So it makes sense to me why they don't group themselves with the billionaires.

Anyways, I think the answer is just based on how you want to define middle and upper class.

I have ~50k/year of passive income. I'm definitely not in the same class as people with ~50mil/year passive income.

"const input$ = sources.DOM.select('.field').events('input')"

Is there a switchMap in here?

What happens if the input element is removed/inserted back into the DOM?

"input('.field', {attrs: {type: 'text'}}),"

It's possible right now for the value in this input to differ from the value in input$.

Maybe use a combineLatest and then this?

"input('.field', {attrs: {type: 'text', value: inputVal}}),"

Pay the 10x developers 3x to join your company. A lot of startups are just groups of very skilled engineers who have identified each other and left a behemoth together to work for themselves.

It's very hard to give 15+% raises at behemoths so there's always people who are very underpaid for what they do.

If someone wanted to sell a new app, they have to get people to recognize their brand and install their app no matter what.

Ride sharing companies then also have to reach a critical mass where drivers and riders can match in a reasonable time. I think overcoming that is the network effect.

This is why I think it's crucial to find a good engineering manager. He or she takes care of the politics for you and makes sure you're properly rewarded for your work. It lets you keep your head down and focus on tech.

They're usually a main contributor and value good code as much as you. They're surrounded by a set of engineers who have worked together for 5+ years. And most of these engineers have followed the manager from one company to the next.

If a company starts treating the group unfairly, they move on to the next company as a group.

Somebody's investment doing well isn't a reason to penalize them. Lots of things have had way higher returns than single family homes.

Yea, the `catch` would probably have to set an 'errors' object on the response. The following `then` would then decide whether or not to throw an error based on that. Not pretty.

Also, I think `finally` makes your code easier to read. I always put the same kind of cleanup logic in there, everyone on the team knows what to expect in that block.

>all savings of people who don't invest in cryptocurrencies are worthless, that fear may be driving a lot of the ICO speculation.

There are lots of ways to invest your money that aren't based on the dollar. Futures, real estate, company stocks, metals.

How about the return on PonziCoin everybody missed out on? It's gone up about 10,000% in 2 months. Market cap should surpass global GDP mid-May next year.

Yes, but all the systems put in place to shield fiat from the booms and busts don't exist in crypto.

For example, the federal reserve and legislators can manipulate the interest rates and the deficit to encourage people to hold or sell their USD.

There are other factors that also push up housing costs. placeybordeaux just disagrees that NIMBYism is the ONLY factor. I don't know if NIMBYism is even the primary factor.

For example, we have a small public transit network resulting in few options for high density construction.

There's a construction labor shortage that will likely worsen.

There's a sudden surge in jobs.

> "A house in San Francisco used to cost at $100k, now it costs $1000k. What happened was a massive influx of new people to San Francisco."

Seems pretty reasonable to me.

I think it's more common among the very wealthy. When part of the appeal is flaunting your wealth, renting is probably not the way to go.

I think a 1000k 1 bed condo is comparable to a 200k car in that it isn't just a place to stay or a way to get from A to B.

It's not like driving the wrong direction. Lets say you build 3 systems and only one gets used. You are still getting 3x the experience and your revelations could end up being very valuable for the system that does get used.

UBI avoids the step function where there is no (economic) incentive up until the "income floor". Policies like UBI could ally people (politically) of low to mid income.

You're in the wrong place. If anyone was going for readability, it'd just be _.sample(['red', 'blue', 'yellow']). 0 chance of OP's bug, 0 chance of nathan's bug. Understand exactly what's going on as soon as you finish physically reading it.

Electron gives you a view process, background process, and a way for the 2 to communicate.

The view process is very limited, just standard web APIs.

The background process is basically a node process and can do anything you can in node.

That list is actually making fun of what you're describing in the JS community. "Not Awesome" is a play on the "Awesome" lists like this [https://github.com/sindresorhus/awesome]

JS classes were extremely hyped up a year ago. Taking a stance against classes was going very hard against the hype.

How well your devs understand the code is the only real metric. If you understand OOP better, stick with it!

There's a lot of reasons against classes in JS. This list has a lot of articles. https://github.com/joshburgess/not-awesome-es6-classes A common point seems to be against the brittleness caused by inheritance (including prototypical) in general. Personally, I find that the tiny amount of performance you give up by using factory and composition patterns is generally worth not having to deal with binding the right context

When a important engineer leaves, sometimes a lot more end up following. Or at least their team members more open to looking at other offers.

I went to App Academy with no degree about 3 years ago. It costed 15k after landing an offer (3k up front).

For my first year out, I made ~80k in the bay area. The next year, my salary went up to ~120k.

I can save up 140k in the 4 years it would take me to get a comp sci degree. Enough for the down payment on a (small) home. I also have 4 years of programming experience on the fresh grad.

From my experience, about 10-15% of my cohort didn't get tech jobs. This is better than the 30-40% drop out rate of college. Also, people who are "just in it for the money" can pursue comp sci degrees as well.

I use none of the technologies I learned there. I could conceivably have done it all on my own. But App Academy put me on the right track.

I did put in a lot of time initially, ~50-60 hours/week coding for my first couple years. But I imagine comp sci majors go through the same thing.

JS has been focused on event handling types of problems while python and perl were used for many other types of problems. You can build a GUI with R, but it wasn't made for it.

To me, it's the event-driven problems JS tries to solve that seems to overlap with typical server functionality. That has been true since the beginning.

I don't doubt that you can. But in a lot of situations, as long as the slow stuff like db queries and api calls don't block, it's good enough. And that's easier to accomplish in JS.

Also, JS is built to handle concurrency. Other languages have event loop libraries, but in JS it comes with the language and every web dev uses it.

Ok, then backend folks just do API integrations and database guys just make tables, no real technical challenges anywhere. Anybody getting stuff done is pasting together libraries.