atsjie

8 ms·

31.
by atsjie 4y ago
I disagree with all three of you. It depends on the use case.
32.
by atsjie 4y ago
This has changed a number of years ago. Basically it's a component-mindset; create some file with everything in it so that in the rest of the app you can just use `<MyButton>...</MyButton>`. The `<MyButton /&gt
33.
by atsjie 4y ago
> if you use tailwind correctly (with @apply) you only have to update it once. "Whatever you do, don’t use @apply just to make things look “cleaner”. Yes, HTML templates littered with Tailwind classes are kind of ugly." That is
34.
by atsjie 4y ago
> How do you enforce consistency in CSS-in-JS? Paddings, margins, sizes, colors? JavaScript variables, css variables? Both can be used. It's pretty trivial tbh.
35.
by atsjie 4y ago
From that link: `<div css={Css.mx2.black.ifSm.mx1.$}>...</div>;` That must be one of the most horrid things I've ever seen done to CSS.
36.
by atsjie 4y ago
`.card-header__buttons` that example makes no sense unless you use global CSS/SASS, which very few projects do anymore. Component CSS/SCSS or CSS-in-JS are very common which resolve this scoping problem. So why bother with a DSL l
37.
by atsjie 4y ago
Separation of concerns went out of the window a long time ago when frameworks (i.e. React) showed that it's better to combine business logic + markup into a neat encapsulated package. Having a neatly encapsulated component that does ev
38.
by atsjie 4y ago
At my company there are like 20-30 engineers involved in search (using ElasticSearch). The code has grown massively and they are all bogged down fixing small stuff, improvements, doing A/B-tests and the like. They also have a whole ETL
39.
by atsjie 4y ago
> If you have 2000 SWEs you'll pay 40k/month just to have access to the website. That doesn't sound like a bad deal if you have to hire such a big build team; let's say you could fire 10 people, 10 * 150.000 (rough es
40.
by atsjie 4y ago
They were not building/re-inventing Bazel (its Open Source from Google); they were just adopting it and ensuring the migration for the rest of the company (which is no small feat, since it affects all other developers in the company).
41.
by atsjie 4y ago
The majority of Golang devs actually do work on web services, API's, or libs/frameworks that would benefit from a standardized structured logging interface. Source: https://go.dev/blog/survey2022-q2-results (
42.
by atsjie 4y ago
Your comment is a bit misleading, I doubt you looked for more than 30 seconds at that lib's documentation given the lack of detail in your response. Just to be clear; I would never use that lib in any circumstance right now, I'd a
43.
by atsjie 5y ago
I never liked promises when they were first introduced because I never perceived this "callback hell" to be an unmanageable problem; there are excellent libraries to manage callback composition, e.g. https://caolan.gith
44.
by atsjie 5y ago
I just checked, it's a BLM banner. Why is that considered political? (I'm not from the US, perhaps I'm missing something?)
45.
by atsjie 5y ago
Seems like a new mod team has already been found? https://www.rust-lang.org/governance/teams/moderation
46.
by atsjie 5y ago
> The products themselves are fine I beg to differ. The majority of their products are flawed and outdated. I'm not talking Oracle DB or Java but the vast amount of other apps they sell. They bought lots of stuff, pull funding from
47.
by atsjie 5y ago
You're right, I stand corrected!
48.
by atsjie 5y ago
From this blog post: "The Terraform product organization has grown in kind, and is now composed of more than 100 people and a dozen teams, ..." From their job hiring page: 88 open engineering positions, ( https://www.has
49.
by atsjie 5y ago
> There's is not a labour shortage of lorry drivers. There is increased demand, reduced supply (due to a pandemic on both counts) - but plenty of people who can drive a lorry and are licensed Not sure what you mean by that, BBC ment
50.
by atsjie 5y ago
I like how this blog focuses on the organizational patterns of DDD in combination with Microservices. My one experience with DDD and microservices was more the reverse; DDD was applied through code patterns but had no organizational/pr
51.
by atsjie 5y ago
Having worked with Mendix and Apex (both low-code tools) for over a year: I wasn't convinced. Anytime you're trying to color outside the tool's predefined lines you'll be hurting and spending ridiculous amounts of time.
52.
by atsjie 5y ago
Don’t agree. Historic context is important to understand legacy codebases, code examples in other resources and colleague’s behaviors.
53.
by atsjie 6y ago
"Timnit Gebru: Google and big tech are 'institutionally racist'" https://www.bbc.com/news/technology-55281862 It's good to be critical and reflect on the company you're working for. There
54.
by atsjie 6y ago
Interesting. I had the opposite reaction towards using classes for this. Mainly because of a fear of misuse. The more options a developer has the less likely he or she chooses the best solution to solve a problem. (Often best is in the eye
55.
by atsjie 6y ago
Couldn't read the article; but might this business model make more sense in Europe or Asia (scooter, cyclist delivery by young people)? Not sure how food-delivery works in the USA, but I'd think the low density, car-focused infras
56.
by atsjie 7y ago
Can't remember ever closing an article I was interested in reading simply because I had difficulty processing the font. The narrow font face on the white background just makes it unbearable to look at, it's so narrow. It actually
57.
by atsjie 7y ago
Been in very similar situation with a CTO/tech lead. I walked away. Didn't have stock though so was easy to leave. Some people are just hard to work with. I had delivered well over 40% of all code changes in a team of 6 devs, but
58.
by atsjie 7y ago
Location found: Northwestern Europe
59.
by atsjie 7y ago
As a manager, would you want an activist person that rails against bad company practices/policy, or a more docile person who only focusses on day-to-day work?
60.
by atsjie 7y ago
This. All teams I've worked for in the last few years basically did this. Although we never distinguished between features/topics explicitly, the proces would be the same. Having one branch per story is just very simple from a man

More ›