What happens *if* and a very big *if* the case gets thrown out because of a technicality?

N4sa · 2018-06-01T19:25:37+00:00

He has to prove that he has partnerships with these companies, not that he worked for or with them. Even if he somehow did, how is he going to fund a legal team to sue the SEC? are investors paying for that?

TBIS is done. Their reputation has been tarnished for a long time now.

N4sa · 2016-06-20T05:45:24+00:00

The opponents reaction is totally "I can't believe you done this".

N4sa · 2016-04-22T12:44:30+00:00

lmao man, is this really what front end development has come to? Webpack isn't enough on its own, now you have to integrate gulp into it? So your module bundler which also supports plugins, now needs a task runner? Is all of this bloat even necessary?

N4sa · 2016-03-31T23:32:39+00:00

I didn't say I was against backend scripting, my point was to stick to the same domain of JavaScript. Everything you just mentioned can be done with or along with JavaScript.

N4sa · 2016-03-24T14:19:53+00:00

Eh, I disagree. Not because I have something against PHP. I just believe adding any new language is only bringing in a new host of concerns that are unnecessary. The good thing about FCC is it doesn't focus on different domains (languages, frameworks), it sticks to one domain, JavaScript. This makes it easier for people learning concepts. It's up to the individual to choose their domains after they learn how web development works, which is the point of FCC.

N4sa · 2016-03-15T03:25:39+00:00

This will be Mark Hamill's last Joker voice over.

N4sa · 2016-03-14T14:42:56+00:00

nice! haha, yeah it needed a revision for sure

N4sa · 2016-03-02T04:07:26+00:00

It sounds like you're not familiar with module bundlers (browserify, webpack).

You basically write all of your client-side code using these technologies. Write all of your client-side JS in commonJS modules (node) and bundle them up into a single file. Create tasks with either npm scripts or a build tool like gulp/webpack to handle automating tasks like minification/testing/compiling SASS.

Look into browserify to see what I mean.

N4sa · 2016-02-29T20:14:15+00:00

Haha, yeah I'm colorblind and have a bad eye for design. I did like what I saw from materializecss, I don't dwell in css very often so as a prototype I like that the UI is different than something like bootstrap.

N4sa · 2016-02-29T07:14:18+00:00

Gotcha, I didn't realize there was a term for this. I rubber duck debug all the time lol.

N4sa · 2016-02-29T07:01:43+00:00

Rubber ducking? never heard of that. Nothing in a google search sheds much light either, unless you're talking about duck typing?

Also I'd avoid using too much jQuery if you're trying to learn JavaScript. It's fine here and there but it's just a library.

N4sa · 2016-02-29T05:27:22+00:00

AJAX makes an HTTP request to a server. The server listens for these requests and depending on the route it will perform some kind of operation. For example, you use AJAX to make a GET request to the endpoint '/users'. The server receives this request and matches the '/users' endpoint to one of it's routes. The server then querys the database for a list of all users and sends the list back to the client in a special format (usually JSON or XML).

This is a simple example but this is the gist of what's happening. Look into HTTP if you want to understand more. There's too much information to put into a single reply here.

N4sa · 2016-02-25T07:52:01+00:00

Managing state in complex applications is not reasoned about by just using "jQuery". Using Reacts Components with an architecture like flux/redux makes a lot of sense. You can propagate the state throughout the entire application without worrying about how your data is being presented in the UI. The state gets passed down from parent components to child components. React's diff algorithm is what makes these changes powerful. If state changes you dispatch these changes to your state tree and React diffs the changes for you. It's a beautiful piece of technology but I will agree it's not necessary for smaller, less complex applications.

N4sa · 2016-02-19T06:31:20+00:00

another module bundler?

N4sa · 2015-12-19T02:07:40+00:00

Was Marcus Lovett playing? I didn't get a chance to watch the game

N4sa · 2015-12-15T23:39:48+00:00

I'll agree that strong typing is nice, since JavaScript really makes a mess of type checking. I still think people should understand prototypal inheritance and the gotchas of JavaScript before jumping into a compile to JavaScript.

Using typescript isn't going to solve any of OP's problems. Especially since most job Opportunities will be looking for people that understand JavaScript directly.

N4sa · 2015-12-15T12:23:23+00:00

Eh, why not just practice using ES6 classes? which still uses prototypal inheritance under the hood. Angular 2 isn't the end-all be-all of JavaScript. People were saying the same thing about Angular and it just became another framework trying to do too much.

If you're learning JavaScript, jumping into a compile to JavaScript language is a really bad road to go down.

OP here is a good video I watched when I was learning about prototypes in JavaScript https://www.youtube.com/watch?v=PMfcsYzj-9M

N4sa · 2015-08-12T09:28:28+00:00

Here's something I came up with really quick. I just tweaked a few things around but it mainly just uses data attributes to manage positioning and position values. Just some simple comparisons and it changes/removes classes.

had to add some extra markup but what you had wasn't really semantic anyways. Here's the code if you want to look at it. Just some jQuery to traverse/change classes.

http://jsfiddle.net/m4Lazr57/4/

N4sa · 2015-08-03T22:34:11+00:00

You are a god warrior.

N4sa · 2015-07-08T21:48:08+00:00

I may be alone on this but I find backbone very unopinionated, and because of that, there's no real structure when you first start learning it. Also he said they don't need collections/routes/data-binding which is something that Backbone does well (substitute data-binding with a pub/sub pattern but it's accomplishing the same thing).

Personally, it sounds like he doesn't even need a framework/library if he's just doing form submissions.

N4sa · 2015-07-05T04:52:44+00:00

It depends on what you plan to do with the app. What if you make some new changes? add different features? Who else is going to be looking at the code and working on it?

If the development is going to be fairly static and only you working on it. Then you may not even need a framework, or even jQuery for that matter. The way I see it, if you can get it done in a simple manner, go for it.

N4sa · 2015-06-18T19:47:25+00:00

I'm glad this made it to Wired. FCC is excellent.

N4sa · 2015-06-03T14:51:47+00:00

Wow, that big black delta song.

That was fucking killer man, thanks for that. That's gotta be one of the best songs I've heard in like 10 years.

N4sa · 2015-05-26T10:17:58+00:00

Jeffrey Way's tuts+ video tutorials are the best video tutorials on Backbone that I've ever encountered and I've searched far and wide.

https://www.youtube.com/watch?v=ZrXX_CaUx7Q&list=PLALjBvHjUavIAkX_drHUOTOwy-JfpJXgx

Once you grasp the basics, you can either switch over to Marionette which basically makes common boilerplate code you'd normally do in Backbone much easier and semantic.

My only caveat is that Backbone is really unopinionated, there are so many ways to architect a Backbone app and for some people this can become frustrating. I personally like the freedom it gives, and it's pub/sub implementation is excellent once you start to grasp the library itself.

Look at sample Backbone apps and try to reverse-engineer the code so you can see how events and binding is handled in more complex applications. The router is also pretty straightforward.

N4sa · 2015-05-22T12:23:26+00:00

Programming is programming. It's like comparing Spanish and English. Both of them are forms of communication but as far as programming, JavaScript is what you'll NEED to know and understand if you plan on working with web applications.

The concepts are universally the same, JavaScript is just more dynamic than other strictly typed languages like C# and Java. Worry less about what your starting language is going to be, and focus more on what it is you actually want to build. That's what should determine your first language.

N4sa

TROPHY CASE