HN user

gaastonsr

89 karma
Posts1
Comments68
View on HN

Location: Merida, Mexico

Remote: Yes (preferred)

Willing to relocate: Yes (within the US)

Technologies: TypeScript, JavaScript, Node.js, React, GraphQL, MongoDB, Kubernetes, AWS, Docker, ElasticSearch, Fastly, Cloudflare, MySQL, PostgreSQL, Nx, Rust, Nginx

Résumé / CV: https://www.linkedin.com/in/gasty/ (will send PDF on request)

Email: gaastonsr@gmail.com

It’s uncommon but it’s used once in a while. I do it 2-3 times a year at least. And believe me, most people wouldn’t even know how to start to do it or would think it’s too hard and prefer to do it in a different way so they don’t need to ever traverse the graph.

MagSafe could be sometimes unreliable. USB C is fun too. Although I don’t like other aspects of the MBP. Like it’s keyboard.

True, and that's why I think a managed Kubernetes service like GKE is the way to go. It's almost like a PaaS but you still have a lot of the control.

It depends on the developer. Myself I like to get in touch with where my code is deployed. So I like to do that stuff myself but most of the time there Is somebody dedicated to that.

That just shows your lack of information on how to manage knowledge workers.

Good managers know how to ship products by knowing how to manage knowledge workers and removing friction in the communication inside and outside the team.

Bad managers IMO. Since their work should be minimize interruptions and facilitate communication inside and across teams.

Working remotely you can minimize these interruptions by turning off notifications. Which in my experience is common. And bad etiquette to interrupt (buzzing channels) unless it’s urgent.

I agree, but you shouldn't map 3 times when you can map once over the data.

   things
    |> pluck('bar')
    |> map(compose(rofl, lol, xor))
    |> reduce(differenceWith('id')

Agreed most problems can be solved by CSS only. My argument would not be we're solving something in CSS, we're simply removing the friction by having the HTML and CSS separate.

I was one of the skeptics and felt CSS, SASS, or Less.js was good enough for me until one I day I was tired of setting up my loader in Webpack and I just dropped in styled-components.

And then my JSX was more beautiful because my tags now had its purpose in the name. And I didn't need to worry about class names anymore. And adding variations (modifiers in BEM) was a breeze. And I didn't need to go back a forth between the CSS and the component to style it. It was just so much better that now I'm a convert. I still can work with CSS only but the convenience that styled-components brings to my components is invaluable.

I hope this sheds some light as to why we prefer to write CSS in JS than writing good old CSS.

I don't see why would anybody would need to migrate anything to grids. It would be more, use where appropriate. In my case, flexbox fixes more of my problems with css. CSS grids will be a nice addition but that's all.

I find this weird. I've been using sublime text for maybe 5 years and it has only crashed once. And it was fault of a plugin, not the editor itself.

Sublime Text has been feature complete (for my liking) for a lot of years now. The only thing I wish it had is an integrated debugger but it's not a deal breaker for me.

I've tried to jump ship to open source alternatives (atom and vscode) but they feel sluggish to me. Most people will be happy with their performance but I've been spoiled by Sublime Text and the slightest delay feels sluggish to me.

I appreciate having more options with css but I do think css grids is coming too fast and it's going to contribute to developer confusion.

Most developers are still getting used to flexbox and now there is something new to learn.