https://www.teagasc.ie/crops/grassland/grass10/clover/#:~:te....
7 karma · joined May 3, 2022
https://www.teagasc.ie/crops/grassland/grass10/clover/#:~:te....
Or define components? https://tailwindcss.com/docs/plugins#adding-components
---
> 1. Tailwind Makes Your Code Difficult to Read
This one is interesting to me. I think devs should take responsibility for writing easy to read code. A framework is a framework. I agree shotgunning classes all over markup is messy, but Tailwind doesn't do that - you do.
I would encourage the author to understand the concepts of extracting[0] and defining components[1] within Tailwind. That can make things very easy to read by the author's logic.
> 2. Tailwind Is Vendor Lock-in
Not necessarily. Especially if components are defined, if anything it makes it easier to change. Because you have a css class abstracted at the same level of your markup. In the world of various competing component frameworks, I would argue the opposite is true. You can just as easily apply tailwind component classes to Vue as to React as to Svelte etc.
> 3. Tailwind Is Bloated
As others have mentioned purge css[2]
> 4. Tailwind Is an Unnecessary Abstraction
"Because instead of repeating styles in your CSS, you’re now repeating them in your HTML", "you’re still writing the exact same amount of CSS, disguised as class names" This just isn't true if you use it correctly again see extracting and defining components.
> 5. Semantics Is Important. Tailwind Forgoes It.
Author recommends BEM and then in the end says "You don’t really need BEM, either". I agree with component scoped css, BEM is less important. Tailwind
> 6. Tailwind and Dev Tools Don’t Play Nicely
What? Anyone who experiences this should revisit CSS order of precedence. It behaves exactly as expected. I've never had a problem with chrome/firefox dev tools.
> 7. Tailwind Is Still Missing Some Key Features
So use css? Using tailwind isn't a binary option. You can use both tailwind and css. It's a tool, use it where it makes sense.
---
[0]: https://tailwindcss.com/docs/extracting-components
[1]: https://tailwindcss.com/docs/plugins#adding-components
[2]: https://tailwindcss.com/docs/optimizing-for-production
[3]: https://jigsaw.w3.org/css-validator/validator?uri=https%3A%2...
Douglas Crockford taught me a really valuable lesson here... in Javascript: The Good Parts he had something directed at the haters of Javascript, that stuck with me. But I think it applies here too. GraphQL and REST are tools/patterns that have pros and cons. All tools have pros and cons. Why would you get mad at a hammer for not being good drill? Because that is what people do in our industry and it's silly.
I tried two years ago to write an article with this in mind, and the conclusion I came to in [0] is that it is an abstraction. Nothing more, nothing less. It's up to the individual to determine whether that abstraction makes sense to them.
Haters are always gonna hate, and I do appreciate your taking the time comparing and contrasting the two. Too often articles that say "Hey wait a minute here, we might be drinking the koolaid for x" come across as contrarian and spiteful. I think you managed to keep a respectful tone while asking important questions. Thank you :)
0: [link redacted]
But I'm not convinced a corporate office is the only, let alone, best option. Have you considered alternatives?
Instead of a bunch of programmers spouting group think, I get to interact with writers, artists, indie game devs, etc. Way more innovative than any programmer group I've been in.
The article points to some statistics about the benefits of remote work. But I think those benefits are more derived from enabling individuals to decide what is best for them and their company. Alot of what is described in "Bullshit Jobs" was reversed overnight, and we're seeing the benefits of that. Location has nothing to do with it.
He's now on a mission to transform the landscape of the city and turn often neglected patches of grass into thriving microecosystems.
[link redacted]
Been an incredibly positive response so far, if anyone is interested in starting something similar we've discussed open sourcing it so others can do in their own city.
Jesus was an incredible person. The bible taken out of context as it is in corporate christianity, really truly doesn't do Jesus justice.
If you love Jesus, read that book - it will only make you love him more.
If you are an atheist - read that book, it will give you a historical basis on which you can critique modern day Christianity.
People are destroying native plant habitats, and creating the perfect conditions for invasives. In fact 90+% of native species aren't threatened by invasives. The invasives actually help heal the soil for native plants.
The author then asks, why then is there a war on invasives? And that's where the book gets good imo.
https://www.goodreads.com/book/show/25782048-beyond-the-war-...
While I agree this is a huge expense, I do question the slippery slope of attacking research budgets. I wish more nations chalked this up as the 'cost of doing business'. Cutting research funding works well for election cycles, but doesn't do much for the folks down the road.
If learning, math or otherwise, doesn't destroy your ego, you can do better. There is no shame in vocalizing uncertainty or a feeling of not understanding. Look at Stephen Hawkings - he had the courage to admit he was wrong and was one of his best critics.
Ego has no place in progress - scientific or otherwise.
Given that, I don't want to be in the room with my coworkers. There's more to life than work.
Not everything needs to be responded to right away, my mind was blown when I first saw an eisenhower matrix. I encourage you to check out this! https://www.google.com/search?q=eisenhower+matrix
I've been managing fine by being available during the day, not stressing and just living in the moment. I get the heavy lifting done early in the morning or late at night. Just like in the office... my most productive hours have always been either before everyone else gets in or after everyone else goes home.
Have you tried holding "office hours" for the newer guys? i.e. give them a window when they can ask their questions to the other devs?
Have you given them an idea of what you expect from them when they're stuck? example here: https://medium.com/@JeffLombardJr/for-new-devs-how-to-ask-in...
People will be on different schedules, but it is nice to have a weekly sync at the beginning of the week. Gitlab and Zapier have alot of great resources on setting up remote teams
- https://zapier.com/blog/survival-guide-to-remote-work/
- https://about.gitlab.com/company/culture/all-remote/guide/
There, I fixed the title for you.