darth_mastah

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

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.