darth_mastah

If this is your personal take, then who is that "we" you keep saying?

What's wrong with Angular commit message guidelines?

https://github.com/angular/angular/blob/master/CONTRIBUTING....

I mostly agree with the article except the part where the author plays down the architectural considerations during project inception.

> Right now it’s just me working on the project, and you can be sure I just cracked open my code editor and started writing code on day 1.

It's definitely fun to start with writing code, but in my view it may be more efficient to pause for a moment, understand the problem and find the right solution for it. Then start writing PoC code, which can be refactored at a later stage. That's just pragmatism - lots of code will go to the bin anyway, but at least we give ourselves a chance to have a longer and happier run with it before that happens.

> I have a bunch of really smart friends who do really interesting things and when we meet up its like what are you up to? Nothing much. Nothing interesting. Later you find out that they just visited Mongolia, another is learning Russian and the other built renewable power system for a holiday house they just bought, but they're too worried about bragging to bring it up.

I love it how you used "Reflected Glory Bragging" (point 9) right here! It's great, I'm upvoting your comment :)

I've been working with the front end for over a decade now in small and big teams, with different approach to CSS. I've seen things go horribly wrong for all the seemingly good reasons. Bloated CSS, people fearing to make any changes to existing "semantic" classes, people making changes to existing classes and introducing unforeseeable bugs in remote parts of the application, you name it. In my view nothing beats functional CSS. It's simple, pragmatic, easy to read and understand. And most importantly it'd hard to introduce hidden bugs with this approach.

> holy hell this is the worst thing I've ever seen

Not really :) It might have been my reaction some 10 years ago, but right now I think it's quite good. I've done BEM, the atomic crap, OOCSS and what have you but to be honest nothing beats composition when it comes to rapid development. I used Bootstrap in the past, it was heavily customised for the project, and I ended up making it look very similar to your approach. It makes sense when you have 20 Devs working on a website and you don't want to end up having separate stylesheet for every page. Because business hates consistent design and always wants this and and that to stand out just on this one page. It should be easy, right? I look at your framework as an embodiment of understanding business driven development in a big team.

> Switching to Linux isn’t an option due to all the design, legal, and other such documents I need to work with frequently for my startup. I can’t risk using alternative open source tools to edit such important documents because the professionals in those areas, are set in their ways and are not going change just for me.

Excuse me, what? Since when editing such important documents can be done only on Mac? That's the dumbest thing I've read all day.

To be honest, I want to see the actual domain I'm on in the location bar, and not some obscured version of it. In what universe is hiding part of the domain an usability improvement? What does it improve? Confusion? Misinformation? Lack of trust in the location showed by the browser? It's so stupid I had to check the calendar to make sure it's not the 1st of April today. I didn't check it in Chrome though, for fear that some days might have been hidden away as they have been considered trivial.

Nice twist with the live updates.

I believe the transitions still need some tummy rubbing. Traversing pagination causes current / next page to appear stacked up and then the current page disappears. Also, navigating between categories (new, show, etc) causes the whole list to disappear and reappear.

On the assets front, nearly 1MB is a bit much for this app. Http2 is a plus, as well as gzip, but the js should really be uglified, there is very little excuse one can make for shipping source code without minifying these days.

> The accuracy would be higher, but there are limited number of comments on HN.

Could you elaborate on that?

So you have to log in to Docker Store on Windows and on Mac. I sort of get the frustration. Using one of these systems for development is a painful experience on its own, no need to make it more miserable.

I would agree with most of what you said except for the point about Linux and OSX. Yes, it used to be like that some 10+ years ago, but not anymore. However I can still find this myth repeated here and there nowadays. These days Linux works out of the box, with no more tweaking or settings up than what is required for OSX.

The paying tier are customers (sort of). All the rest are product. It's quite a specific product, because it has to be seduced and tempted by perceived benefits to forfeit its privacy, but still a product it is.

> Is this an IT thing, or is this phenomenon known in other areas, too?

This phenomenon is certainly known in fashion and, looking at the boom of populist and nationalist politicians around the world, most probably in politics too. I would even risk saying it's imprinted in human nature.

Apple cast away Steve Jobs and then came begging for him to come back. He did and steered the company from the verge of collapse to a massive worldwide success. Since SJ passed away, Apple is getting worse each year. I guess this might be Jobs' spirit fading away and people thinking they could do better than him. Clearly, they fall short.

I'm sorry, what criterion other than the commute time do you use to determine who "needs to" work from home? Increased productivity while working from home does not simply stem from lack of commute. It's all in the article.

I have great respect for Richard Stallman, but frankly this text seems a bit paranoid. So what if they know what I watch? Is it too bad if I can have a list "continue watching" to pick up where I left off? Is it that terrible, that they can suggest to me other content I may be interested in? Is it a crime that they want to know how their service is used in order to stay attractive? I think not.

I've always been a slow reader. There was a time when I considered that to be a fault. I tried to learn faster reading a number of times, but each time I found it unnatural and not very enjoyable. I have also noticed that reading slowly allows me to focus better and gain deeper understanding of the text. At some point I stopped trying to become a fast reader and now I'm just a slow, happy reader.

Maybe I don't understand the Article 11, but does it essentially mean problems for Hacker News?

The author draws conclusions based on a sample dataset of 4000 submissions, whereas currently there are 2,962,457 submissions (stories, askHN and showHN combined). Seems a bit risky at best, unless the sample was designed in a very clever way.

> “It’s very difficult to label the underlying emotion,” he said, since external expression and internal feeling don’t always correlate well.

Not true. Paul Ekman spent most of his professional life studying micro expression and he developed pretty accurate system for recognising emotions leaking though micro expressions. The science presented in the TV series "Lie to me" was largely based on his work. https://www.paulekman.com/

It's as if you were describing my own experience. With the only difference, that I had to figure out how to use vi. Such fun! I took me some time to figure out how to exit the editor, let alone how to make changes or write the file.

We didn't have all the resources at out fingertips back then. Just the books. We couldn't find copy-and-paste hideous solutions on StackOverflow, we had to figure it out on our own. Programming had the air of wizardry.

I do believe that nowadays it's much easier to learn the basics of programming, considering massive number of resources available just a few keystrokes away. On the other hand the expectations have changed a lot after programming went mainstream.

In my line of work, before I became a consultant, I had interviewed a lot of candidates for web development positions. In my rough estimate only 2 out of 10 are cut out for it. And no wonder - the demand on the market is massive, the money is all right, so more people jump on the bandwagon and try to get by. They don't want to learn a great deal, they don't have a real interest in the domain. They just want to do the job as painlessly as possible and get paid good money.

This also means, they have to cut corners. They don't have time to figure things out and build solid foundations. They are after quick results. They just want to become employable. The passion in our profession is hugely diluted, with the inflow of people who want to do the job just because it pays nicely. It's pure economy.

And because it is economy, the expectations have changed. Maximising return on investment, where the time spent on learning something is the investment, means that steep learning curve is no good anymore.

So maybe let's not dwell on how hard it is to become a programmer these days. In my view it's definitely harder to stay one, than to become one, with everything changing so fast. However becoming a programmer is not more difficult today than it was 20 years ago.

This is great. Does it mean we finally have cure for cancer? My granddad died because of that shit, and so did my uncle. Maybe there is still hope for me.

> The author seems to think that React users choose Flow and Angular users choose TypeScript. > However, TypeScript works really well with React and has for a long time.

I don't believe the two statements above contradict each other. React users can prefer Flow even though TypeScript works with React. In truth, I believe it's only natural to choose Flow if one is working with React. After all both are FB creations and are meant to work together out of the box. TypeScript on the other hand is promoted in Angular documentation. Considering the above, it's really hard not to get an impression that most devs would choose to work on well supported pairs: React+Flow and Angular+TypeScript.

+1

It's all fine and dandy except Amazon could not handle the volume. Two of my guaranteed next day deliveries were awfully late, one of them over a week. Apparently my case was not at all isolated, as people were complaining all over the Internet. Reading their boasting leaves quite a bad taste.

Same here. +1

Depends on the context, I guess. While working on a code base employing DOM manipulation it's absolutely fine. Having said that I would think long and hard before starting a new project with jQuery, and then probably used another library. There are other ways to get things done quickly, efficiently and in a way which promotes maintenance.

Considering current trends for creating complex applications for the client I do not believe jQuery has much of a future anyway. It had been good while it lasted, I used to like jQuery a lot until better tools came along. These days libraries for DOM manipulation seem not only obsolete but also standing in a way of focused and efficient development. Let jQuery rest in peace and be remembered for its past greatness.

> I don't think that after 12 years you can say it didn't work for Munich. It worked for 12 years and now, for political reasons, it's going back to Windows.

Very good point. Also, it's really sad to see political agenda driving technological decision making.