georgefrick

As a developer who didn't care for Angular 1.x and strongly argued in favor of a simple approach for years (Backbone, etc).

I've been using Angular 2 in a major enterprise project since RC1. Even with some of the headaches between RC releases; all of the reasoning behind those changes is technically sound.

It's easy to write components and wire everything, and even small things like async validators are fluid and easy to implement.

I'm loving it, and while the entire build system is still a bit of a dumpster fire; we're doing great on things like testing, code coverage; etc.

There are a lot of problems with lazy developers hoping a blog will tell them how to do every little thing. The source code is on Github. If you can't get something working right; maybe go read the source code of the classes you are interacting with. I've found 99% of the time now that simply reading through the code gives me not only the transparency needed, but a clear path to a better solution. Kudos to them on the new forms; they're awesome.

I've been working on an enterprise app with Angular 2 for over a month now and it's been mostly ok. I think the only horrible problem was the change in the form framework that went largely undocumented (super secret doc: https://docs.google.com/document/u/1/d/1RIezQqE4aEhBRmArIAS1...)

Once you get to forms 0.2.0 and rc4 of everything else; the framework is beautiful and even though I hated Angular 1.x with a passion, Angular 2 is awesome.

Java, sometimes node/js on side projects.

I'm using ts-loader, have you tried both and found awesome-typescript-loader to be better? I'm trying to decide if I should switch to it..

I have some advice for the author.

Go back and edit this; remove the big middle finger image and tidy this up to be more professional. It's ok to write it (kind of), but seriously you made a "fuck you" logo?

Would not hire, or interview, or want to be associated with professionally.

There is an error in at least one example, it's small but confusing to run into:

var sonalisTemp = get(sonali, "name"); // sonalisTemp === 22

I think you meant

var sonalisTemp = get(sonali, "temperature"); // sonalisTemp === 22

It actually bugs me every once in a while when I do an interview and I know the guy can code but he just can't articulate anything. It's like he's locked in there and he would be fine if I slipped tasks under his door in an envelope. But to your point it just doesn't work that way and those people get turned away not because they didn't have the technical skills, but because they demonstrated they couldn't be effective beyond the IDE.

The other day I finally cut a guy off and said, "Yes, sure, you aren't good with terms and explanations. How do you have technical discussions with other developers? What do you do in code reviews?". Deer meet Headlights.

I also realize your point is beyond technical communication, and you are right on that too.

My GPA was not awesome.

You could be affected by any number of things (wrong university, wrong goals, wrong order of operations, in a hurry). Please don't be offended, I just mean that you might leverage your resources better and find classes you care about (I ended up double majoring in CS and Economics, but I didn't care about econ until I tried it).

Here is a more plain and TLDR response. Pretend it's a new investment and write down/spell out what you are putting in and getting out. If it doesn't add up, don't make the investment.

Finally, not caring is a problem. For some arguing in favor of degrees, this is a big part of their point. Why don't you care about those classes? Do you think you'll only ever get cool and interesting projects at work? An employer needs to know you'll spend two weeks finding some ridiculous bug that doesn't even affect anything if that is what they assign. Every third Sunday, the system crashes. Fix it. While your peers do greenfield work. It means sometimes putting effort into things you aren't interested in as part of the bigger picture.

I'm actually confused why you seem to be attempting to argue my point, when I was stating it's a situation that is unique to an individual. Do you really objectively think a degree is a yes/no answer that applies universally? What if someone wants to work on deep sea exploration robotics? Yes/No is an oversimplification and your post actually helps to point that out in two ways.

The second way is easier so I'll get it out of the way. More education earlier is an argument that formal programming education can be helpful. That wouldn't undermine the idea that a CS degree has importance on a individual basis; not as a general yes/no rule. We've agree that formal programming education CAN help.

The second point is big for me, and it really bothers me to be honest (not about your post, I appreciate your post). It's this idea that the CS degree is this static cement thing; like we order it from Amazon. A degree is what you make it!

Your point about remedial classes, etc is spot on. It's exactly an argument that each person has to weigh the benefits they can get from the degree with the benefits from going right into the industry. If the person shows up at college and picks programming for the reasons you described; then you are probably correct in that it is not "better". However, college is a four year chance to build a competitive advantage. Statistics. Economics. Linguistics. Physics. Accounting. Art. Etc.

If someone chooses to make their degree a worthless money sink, that does not cancel out the person who spends four years learning to code, analyze speech, and working hard on the OpenROV team. Those are two completely different people and neither needs to put their degree on their resume. But only one can put speech analysis and OpenROV there; which they got as part of that degree. They also now have those contacts and team building experiences. Another example might be someone who spends the four years working part time as a contractor. "Got a degree while building industry experience" trounces "got a degree" AND "industry experience" (imho).

A degree is something you pay for, it's an investment and should be treated as such (in the scope of our discussion). While the underlying argument may be if an employer cares; I think that honestly employers are looking at it as a signal that there might be something more to you than some Java/JavaScript syntax.

I'm not sure I would so quickly listen to the HN trends. There are a lot of people on HN who are younger and they like the idea that this would be a trend. You are allowing them to define the competitive advantage.

You'll have to do the math and weigh the cost/benefits of your degree.

Personally I think we're in a bit of a bubble/gravy train. The idea that programming will become the new automotive assembly line for self-taught labor is a bit of a stretch.

A degree can impart many benefits (math, core CS ideas, subject matter classes such as speech theory, advertising, management, etc). While many people can make enterprise apps with direction based on being self taught; not many can really build something in depth. Boeing isn't going to let just anyone write aerospace firmware. So if you want to get a job quickly and milk this while it's hot - maybe you go for it? I don't think it's clear cut, and I like having my degree. I'm good friends with fantastic developers without degrees who work alongside me.

In the long term; it depends on the competitive advantage you can get out of that time in school vs your peers extra experience in the field; as well as your goals.

Are you a stand alone contractor, or do you work for someone? How much experience? You'll have to excuse me for bugging you; but I have 10 years experience and I make half that.

Nothing is wrong with Backbone. I thought it was beautiful. We don't always pick our tech though. It's part of the problem here; the hype engine is used to steer non-technical people, or more managerial technical people. While the engineers and technical leads might be completely comfortable; the next project starts and you are told it should use X since that is what the client kept mentioning when they called.

Also, some people love this. It means they can show up at work and talk about how they learned React and it's better and they can do a pretty good job of using the hype train to stand out from their peers.

"I don't get paid to write blog posts defending Angular, so I don't bother."

I really like this comment; because it resonates with my Backbone experience. I kept reading these hit pieces by Angular fans as part of my daily info gathering; but I had code to write and a project to deliver.

But not writing those blog posts may have been an error on our part; we avoided the discussions and it leads to the cool kids changing the rules all day.

I can't force you or I to write these posts; but maybe we have to face that there is a cost to not contributing.

"It's pretty clear... is the direction the industry as a whole is going".

You or anyone else posting hasn't identified this "industry", it appears to be "quickly built apps that have no lifespan". I mean no offense; but we're back to saying it should be used because people are using it.

I'm upset at exactly that; it's not like anyone replied with objective software development reasoning that justifies this constant shift of frameworks, or addresses the need for enterprise software to have a longer horizon for support and talent.

I'm not a fan of these discussions at all. We're all supposed to have been using X framework at X time period. In the enterprise we can't just keep rewriting all the god damn applications.

For us contractors, we have to answer to clients we had 2 years ago about why their app is in Backbone.

I mean, damn; we have to build software here and we aren't all Facebook. You might get warm and fuzzies from constantly starting over and feeling like you've chosen the right framework, but it's immature.

Oh, we got it right this time! React is a paradigm shift! We've quickly forgotten we were saying this with Angular bindings. Oh your model based stuff is crap, this has TWO WAY BINDING, it's a paradigm shift!

Now, I'm using Angular. I could recite the Backbone source code, we had a few small libraries and we built huge apps and they worked (and they were built with Grunt and it worked fine, but hey, move it all to Gulp! now! Paradigm shift!). In this case I was expecting it. I waited six months and Web Pack came along.

We're going to go ahead and build our app in Angular 1.x with TypeScript and Web Pack and test it with Jasmine.

This article is NOT correct. This hasn't been 'decided', there is no clear winner. You can't simply list the features of something as "amazing" and "where it's at". You are arguing finality here and you main data point is "coolness factor". It's not correct, it's not objective, and it isn't high quality, long term; well thought out software development practice.

I'm working in Angular now. I miss Backbone, and fully believe the applications we built in it are strong, supportable, tested and expandable. They increased my reputation for fast delivery and high quality.

But, the technologies aren't usually our decisions, and "what's cool" is generally what wins :-(

I found your addition very interesting. But I think the "Tesla fans" referred to, are referring to something different.

The Tesla vehicles are "missing" a lot of parts that rust, corrode, and cause engineering challenges. One of the main ones behind the exhaust system. Speak with a series of car mechanics and they'll invariably tell stories of cars that never received an oil change until something fails. There are videos, pictures, and documentation of Tesla being able to swap drive trains, etc.

Put together, Tesla is able to better protect the frame and body from corrosion by separating it from the same parts that usually "Carry this along". That's a lot of text to say they reduce the surface area and mass of corrosion and failure prone parts.

This isn't to say I agree, but I find the information all fascinating (as a car guy). The best way to make a car, in my mind; more serviceable is to increase the protections from rust and corrosion. Otherwise a simple brake pad ends up being an entire brake system upon repair attempt. In regards to electronics; they can go in sealed compartments and be easily serviced. How awesome. They can also just as easily be replaced by a superior implementation.

Anyways, your post made me ramble a bit but I'm trying to determine if I agree with the original post or not.

I didn't know it was a locksmithing term, that's actually interesting and I'll have to Google a bit. It also puts the comment into context; but I was probably not the only one to miss the whooshing sound.

You're on HN, everyone is talking about a small distinct sector of the country where all of this is insane. I've been in the conversation on here before. Leave the west coast of America and the salaries normalize quite a bit. There is literally a 'gold rush' right now of people moving west to work in tech with no thought to the cost of living.

I wasn't proposing illegal activity. I was in an obscure way, pointing out how badly insecure devices are actually a double threat. They are a threat in their own right, but they are also a threat in that you can't assume they haven't been tampered with.

I didn't down vote your comment or anything; but I think the general idea is to add to the conversation. Short quips generally turn gray... the rest of the thread under mine is mostly discussions of security options/concerns in regards to firewalls and networks.

So, you could; buy lots of these. Take the bulbs and hub and modify the software further. Since they come in a 'box'; you can put them back in the box and then give them to people as gifts or promotional items.

You are now behind their firewall.

If you are a hacker and you manage to get into a factory in China or Taiwan or wherever that is making these; you swap out the base firmware with one of your own that dials home. You are now behind the firewall of all customers.

Just some random thoughts before bed.

Not necessarily; all hobbies simply become social. Gunpla? You go down to a anime store to do it with others. Kayaking? Storage facility the manages the kayaks and can rent personal storage. Robotics? You'd head down to the local Maker shop and rent storage/locker. It's simply becoming "social".

I'm not saying I agree or like; just that it doesn't mean giving everything up.

But.. There can be benefits to building a robot in a room where you can go on the slack channel and ask for a part... or kayak with someone new similar to going for a round of gold with a new partner.

We have the same problems with taxes. Corporations can play the states against each other in regards to 'bidding' with tax breaks. But I think citizens should do the same there; tax breaks in return for shares. Either way what really has to happen, is for gov't officials to resume responsibility for negotiating for the people instead of for themselves.

That said, I make no argument it's a great choice. The public probably shouldn't be "investing" and like many would argue; it's a bit of overstep by the government to be managing team ownership. It's all murky but inextricable.

Money a city gives towards a stadium should be returned in the form of shares in the team. Otherwise no deal. St. Louis should be selling their shares to LA for a profit right now...

You can get the treadmill attachment for the evodesk. It's 999.00, so about $1800.00 total w/desk.

Arguments from the project/push add to url would be great! A page outlining why you are better than gitblit would help with clients :-) (who are all possible future EE users)

Can you suggest a good way to get started with Ansible?

Can you comment more on why a hobbyist should not need their own repo? If I'm doing SaaS for everything, my monthly costs start to go up. I've found it is far cheaper, and far (way!) more educational to take an extra box out of the basement and install Ubuntu/GitLab/Node/Java/Apache/Etc. I have to pay for internet either way, and the electricity cost is nowhere near the cost of having multiple Saas?

I've been using GitLab myself and suggesting it to any clients with the proper infrastructure. When I found GitLab I tried it out, and finally ended up moving my SVN to Git (private projects). It's a great piece of software and I love the web hooks.

No warning, no error, mobile safari just kills the tab. It's not fun. Optimize images, optimize audio, stream audio, stream images, reduce text, pack text, pack everything. Repeat, repeat, repeat. Still crashes. How do people work with Apple stuff? I got a macbook and xcode, it lets me view logs/etc, but nothing helpful.