r/programming • • Sep 15 '16

Angular 2.0.0 officially released

https://www.npmjs.com/~angular
1.3k Upvotes

535 comments sorted by

View all comments

Show parent comments

42

u/dedicated2fitness Sep 15 '16

Question: as a backend dev(C++/Java) trying to get into frontend stuff, how the fuck do you keep up with all this stuff? i'm still trying to master basic html/css/js and there's tons of stuff like SCSS and node and typescript, react etc that people keep talking about and a lot of it(forgive me if i'm wrong) seems to be syntactic sugar for the base languages
like how the fuck do you keep up? would you define a good front end dev as someone who can build something from scratch without ever peeking at a manual/online help forum coz i can't even seem to set up routing without going through an hour long deep dive into someone's personal blog :(

26

u/Jukibom Sep 15 '16

like how the fuck do you keep up? would you define a good front end dev as someone who can build something from scratch without ever peeking at a manual/online help forum

Good god no! There's a lot of tools and it's completely unreasonable to have to know them all. I find though that having a few working projects on my system utilising a bunch of things I want to use often helps as a really fast reference. So as with anything, practise!

12

u/dedicated2fitness Sep 15 '16

as someone who comes from companies where "google it programmers" are sneered at, front end dev scares me. am trying to practice and lose my attitude of "you have to know it all before you try something"

50

u/Jukibom Sep 15 '16

Honestly that just sounds like a really shit culture. Sure, if you're a stack overflow ctrl+v programmer but if googling a problem quickly leads to a solution or a link to the documentation where something is explained, it's kinda fucking stupid to discourage it.

16

u/dedicated2fitness Sep 15 '16

it is a shit culture and i'm trying to move out of it

9

u/GroovyLlama Sep 15 '16

For starters, I just want to say that I love Stack Overflow. It has helped me solve issues on a number of occasions. That being said, there are a lot of programmers out there that just copy/paste the accepted answer from SO without understanding how or why it works. Not only does this not help them become a better programmer, I have also seen it cause issues because the top answer is not necessarily the correct answer. If you are going to SO to find the solution to a problem, please at least take the time to understand what the solution is doing before blindly copy/pasting it.

0

u/[deleted] Sep 15 '16

[deleted]

→ More replies (5)

7

u/centurijon Sep 15 '16

It helps to keep in mind that software is constantly evolving. About every 3-5 years there's a reasonably sized shift in what defines "modern" programming. Keeping up with everything is impossible, but knowing how to research technologies and patterns is what prevents a good developer from becoming a dinosaur. And I mean that almost literally - don't stay unfamiliar with tech for so long that you become extinct/obsolete.

12

u/SurlyJSurly Sep 15 '16

This is an artifact of the webdev community and doesn't come close to reflecting the industry or software design/development at all.

Basic design principle/pattern/algorithms haven't changed in decades. Even the latest "hotness" of functional programming was what I was doing in college 20+ years ago (and is much older than that). Sure that was in Lisp but the principles haven't change. OOP is still relevant and will be for decades to come.

All these front-end JS frameworks & libraries are just the latest implementation of an MVC/MVVM that has been around for ages. If you know the concepts, the rest is just syntax.

4

u/centurijon Sep 15 '16

The web is definitely an extreme environment for this, and the underlying patterns are all there. But if you think about things like TDD, IoC, even functional programming - they aren't new concepts, but they are new to being mainstream. Even MVVM has only been around since '05, and didn't start getting a good amount of traction until '10ish.

You can say it's all "just syntax", but if syntax didn't matter then we'd all be using one programming language.

→ More replies (2)
→ More replies (2)
→ More replies (2)

26

u/timmyriddle Sep 15 '16

Tell me about it. I've been working in the frontend world for a few years now and sometimes it makes me want to throw my keyboard in the air, punch my monitor, push my desk over, head out to the countryside and live in a cabin in the woods.

You're absolutely right: most stuff is fluff that makes life "easier". I have to remind myself that 90% of the confusion in the frontend world is because of tooling. I don't need gulp, I don't need sass, I don't need frameworks. They just provide a means to an end: the choices I make in building a web application today probably won't be the same choices I will make next year.

Add in stuff like continuous integration, testing frameworks, deployment/orchestration tools, and it all gets too much. Ironically, once the tooling is taken out of the picture, things look decidedly easier.

Part of the problem is looking at other people's code and trying to follow what they were doing. I remember my face contorting into a tight frown when I'd be following a tutorial, head over to the repo and wonder why there were twelve different folders and a load of files with extensions I didn't recognise. I'm supposed to building a navbar, what's this .jscsrc thing?

Good advice I received early on was to focus on learning pure JS, not on the frameworks. Angular 1 was particularly bad because of its obtrusive syntax, it almost felt I was writing code in another language. I understand that 2 is much better.

More good advice I received was to pick a framework based on your best guess at the time and try to stick with it, don't fly around trying to learn them all. Each one has strengths and weaknesses, it's better to know all the nooks and crannies of one than to know broad strokes about a them all.

As regards keeping up with everything, my advice is don't bother. Learn JS, work out what tools work for you, and just keep up with the honoured list of components that make up your development environment.

If it's any consolation, I don't have a clue what I'm doing, and most people I talk to don't have a clue either. You C++ guys are a little scary because you seem to have it all worked out with your fancy ISO standards and working committee.

2

u/Labradoodles Sep 15 '16

I would say that the best way to go forward right now is get babel working and work purely in the new new of the Javascript language. There's so many features that are amazing and help manage complexity and ship smaller bundles of code.

I was writing shitty jQuery calendar logic and moved over to using ES 2015 and it was like suddenly everything was a bit easier and more straightforward. I wasn't importing full libs for tiny amounts of functionality and didn't have to roll my own which wasn't as useful.

But you are correct. At the end of the day whatever you decide make sure it's making things less complex not more.

23

u/sirin3 Sep 15 '16

You do not, you just start making your own framework

That is why there are so many

0

u/[deleted] Sep 15 '16

[deleted]

6

u/[deleted] Sep 15 '16

So basically we are just implementing native apps that are slower, reimplementing all the libraries.

7

u/Pawn1990 Sep 15 '16

Typescript, Coffeescript etc with Requirejs is also a good way to abstract some of the painful javascript.

But yes its the case of people wanting a "standard" so they build their own framework, which then becomes one of the many frameworks out there..

Revalent xkcd

→ More replies (2)

23

u/ellicottvilleny Sep 15 '16
  1. Be opinionated just like you already are in your choice of backends.

  2. Learn one framework.

  3. Pretend everything else sucks and ignore it.

6

u/dedicated2fitness Sep 15 '16

am not opinionated in my choice of backends, just fell into them through opinionated professors/tech leads and lookin for a change
but if i am right in my learning of web development so far, the process is

  1. Blog extensively about your learnings of a particular framework

  2. Make your own framework and hoodwink people into using it, thus guaranteeing your employability as "he's THAT guy"

  3. Never make anything worthwhile in public again coz it's not worth the hassle

10

u/drainX Sep 15 '16

I wouldn't put Typescript in the same bag as all those frameworks. Typescript is just a way to make working with Javascript not a completely horrible experience.

2

u/dedicated2fitness Sep 15 '16

it's still stuff i have to (choose to) learn on top of javascript for not much more apparent benefit as a newb

→ More replies (6)

5

u/Regaez Sep 15 '16

Lots of reading, mostly in my own time. Sometimes during work if I have some spare time. Also experimentation on my own little side projects to try out new things. Most of them go nowhere. You can't know everything, so I just dabble in things which interest me, or are areas/subjects relevant to my work.

I am using React every day for work, but damn me if I had to set up a project from scratch. I would definitely have to look up documentation, simply because starting from scratch isn't something I have to do very often. I don't think that prevents me from being able to be a "good dev".

5

u/i_spot_ads Sep 15 '16

like how the fuck do you keep up? would you define a good front end dev as someone who can build something from scratch

That's not how it works in web development, frontend or backend. Knowing how to build from scratch is good, but in real world, web development is a really dynamic process, you gotta know how to use different tools to go fast and minimise the cost of your product, the trick is to know the right set tools, not all of them obviously, we're not reinventing the wheel here, where using it to build cars that people will use in their day to day life..

4

u/JorgJorgJorg Sep 15 '16

I am a backend dev and from 2013 to 2014 I and 4 others built a pretty large angular app with the java backend written by another team.

It ended up being a huge advantage that we approached it as backend developers. We didn't write our first feature until we had a complete build and deploy pipeline created in grunt (which didnt take long) and when we did begin to code our knowledge of backend patterns were susprisingly transferrable to angulars architecture.

In the end when I compared our project to one that was built by front end developers, I could tell that their lack of experience building large backend applications caused them to completely misuse or omit maybe 50% of the things that made angular/jasmine/grunt so cool.

So just jump into it with a solid project in mind and I think your background will allow you to become bery capable very quickly.

→ More replies (1)

0

u/[deleted] Sep 15 '16

[deleted]

→ More replies (1)
→ More replies (11)