343 karma · joined February 6, 2013
I'm linking my keytrace.dev: did:plc:uashgn65n5z7aqwk5cbuba5c
source: I committed it.
Also, a single company provides limitations - you've got blinders on, and your project isn't open for those with a different perspective to come in and take a look and notice something. I honestly think that fresh, open, and global perspective is truly key the success of OSS.
This article mentions increased use of OSS libs as a rising source of XSS. I'm really not sure what's worse - OSS that can be fixed and audited easily or proprietary software that's closed and lacking visibility.
This is a problem with how it's interpretations the encoding of characters - they should be escaped by default and be able to be enabled with a flag if there's a valid use for them.
The reallllly important thing is that you're not calling your chat app TinyChat, but Tiny. If you are calling it TinyChat and started after they opened, you'love need to reassess. If you're calling it Tiny, then you're better off.
Not a lawyer, just what I've experienced the laws around this to be.
While I know installing ad-block is still opt-out (not -in), it's still a choice of a click that I'm making. I want to support you, but I don't want the choice of privacy made for me.
The closest that I can get to is a class that's half HTML+CSS and half WordPress. All other similar classes are Computer Science, and are languages like C++, C#, Java, and Python.
I know it's good to learn those, but I'm under a tight schedule in terms of credit hours, and can't afford to take extra classes outside of my curriculum.
Everybody, and I mean _everybody_, has their framework, platform, language, and so on that you should learn. If you ask a question like this over an extended period or in a popular forum where it will get seen and responded to, you're going to get a million people telling you to go in a million different ways.
_You_ need to take a look around, and figure out what's best for _you_. Pretty much every established framework, platform, and language is good.
You can build an app with any of them, but some have special characteristics that might seem more relevant to your interests. You should evaluate probably 5-10 of each of the available options in each category based on the features they specifically point out that they're good at, and choose which ones you want to use. Here are some of the different frameworks/platforms/languages you can start with:
MVC-ish frameworks:
Angular: https://angularjs.org/
Ember: http://emberjs.com/
Backbone: http://backbonejs.org/
React + Flux (my pick, as it's pretty revolutionary):
http://facebook.github.io/react/
and
http://facebook.github.io/flux/
Server-side:
Ruby on Rails (the most common server-side framework, but slowly fading out as a favorite): http://rubyonrails.org/
Node.js: http://nodejs.org/
io.js (my pick, as I'm involved with it, and it's 100% a step up from Node, as you can by default use ES6 (search ES6 on Google if you don't know what it is) features): https://iojs.org/en/index.html
Django (Python): https://www.djangoproject.com/
Client-side JS:
jQuery: http://jquery.com/
Plain JavaScript (my pick, as I feel it's a lot more healthy to learn vanilla instead of rely on jQuery as a crutch, which is what most, but not all, front-end devs that use it do): A million tutorials online. https://developer.mozilla.org/en-US/ for docs on functionality. Find extremely well-designed (visually) blogs that have tutorials on how to _build programs_ that have actual usable functionality in the browser.
If you want any more advice or guidance, hit me up on Twitter @bitandbang or email me at bitnb@subvertising.org.
That said, there's no information once you log in, either. You're just taken to a feed, and left to your own devices. Not what I'd call a great experience. I like the idea, but you definitely need to develop this more.
I tried to take a Comp Sci. course last semester, but I knew everything that was going to be covered--logic, loops, functions, etc. The basics. You'll encounter the same thing at any college with a Comp Sci. degree.
However, you'll also find that there are much more interesting topics that are taught the further you get in. You'll like it more and more as you go, and you'll learn more and more too.
Something to know is that college is more than just learning to program. College is an experience that attempts to make you a more educated person for the rest of your life. The topics covered will go outside your comfort zone, and that's a really good thing. People who are successful at college know that they're getting much, much more than a certification for their job of choice.
Many people will tell you that college sucks, and you don't learn anything. Trying to be kind, that's because they suck at college. They were the kind of people who partied until 12 hours before their final 7 page essay was due, and were so plastered that they pounded out a steaming pile of hot brown stuff. They say college sucks because they didn't do it right, and so they feel like it is inherently a bad deal.
It's not. If you do it right--do all your work before the last minute, be an active participant in your college community (organize hackathons, run a {insert language} club, enter your work in student shows), and actively network with professors, you will succeed. Get your work done as soon as you can, make good progress if you can't finish it in one sitting, and you will still have time to do things like have side projects, be on social networks, and have freinds. Don't settle for anything less than an A.
If you want to talk more about this, feel free to email me: bitnb at subvertising dot org.
Also, if you keep hacking away at side projects until you get a few successful ones under your belt (like tiny libraries, for animation, forms, markup, the command line, etc.) that will also show that you're competent and know your stuff.
Just wanted to say: Fellow college student here. I'm still working on getting the first real foundation of programming down, but I think we're in a pretty good spot.
This is a carbon copy of my life as a programmer right now.
I've made the decision to just fucking do it about 50 times, but each time I get barely started and get so frustrated with myself for not understanding and not knowing what to look for that I give up. I know that's another point where I just have to sit, searching, until I find the answer, but it seems that from my profound lack of understanding of the basics of the language (JavaScript; despite doing the Codecademy course, and the CodeSchool Node.js and Express.js courses) that I will have to do that for every minute step that I take in the program. It just seems so overwhelming that I become paralyzed in my desire to push on, but feeling that I know I won't make any progress.
I just don't know how to actually _do things_ with code. So, in essence, I think I know the language, and in a sense I do insofar as I know how to write an if else statement, a while statement, declare a variable, etc., but I _don't_ actually know the language, because I can't do anything with what little I do know.
Do you have any advice?