I sent some money to a colleague's PayPal account who was collecting money for another colleague's leaving collection. I used the name of the colleague who was leaving as the note/reference on the payment.
A few days later I received an email from PayPal asking me to provide the date of birth of the colleague who was leaving and that the money would be held until the request was resolved. They claimed it was to meet regulatory obligations.
I called them and said I refuse to provide the info because I felt it breached GDPR laws and besides, it had nothing to do with them.
I came across this attribute when making a model/popover widget to capture focus, which is necessary for accessibility and keyboard navigation. Works great and will be using again.
I've seen this sort of comment many times, implying that indicators, flashing lights, use of the horn is unique to certain countries or regions. Yet every time, there's replies saying "hey I'm from <region not mentioned> and we also do this".
It seems to me people haven't realised the behaviour displayed in their part of the world isn't as unique or quaint as they think it is!
There's Headwind CSS, which orders classes predictably. But it doesn't move them to separate lines. This could be a config option if you're willing to write a pull request.
I used to make music with Fruityloops between the age of about 14-20. I never got that great but pleased with a few tracks. Still have hundreds of "demos" on my old hard drive.
Nah, I'm very confident with CSS and I prefer functional classes. It's just a far more efficient use of my time to not have to write CSS when there's no need.
Yes but you shouldn't do that really. You should use a view templating system instead to recycle the patterns you spot, e.g. button.tpl would contain the abstraction of classes.
The moment you collapse the classes in to a single class you're back to square one and the reason functional CSS arose be first place.
Adam Wathan promotes this pattern himself in this video.
I've only started using Tailwind specifically in the last year or so, but I've been using functional CSS for about 6 years.
I don't believe using @apply is a maintainable approach. A better approach is to use view templates. In fact Adam Wathan recommends this way too in this video https://youtu.be/J_7_mnFSLDg
My team has been doing this almost all the time since we went remote in March. It works well for us.
It helps more junior team members as well, since they're able to watch how more senior people figure stuff out and ask questions whenever they like.
It also has the social element, which many people have mentioned they're lacking while working remotely.
As long as you're on a team with people who can communicate well enough and are happy to have their camera on, it's great.
I've only had issues when there's someone who is just lurking without a camera and they seem to refuse to turn their camera on for whatever reason. They're making people forget about them and they miss out.
If all the employees of a company based in NY work remotely, wouldn't the company just relocate somewhere else to make it cheaper for all the remote employees since there's no longer a need to have a HQ there?
I don't see that as an issue. It will get cached and it's the same difference as having a medium sized, well compressed image. Almost inconsequential when you consider you'll never have to write any more lines of CSS.
Don't get so hung up on the size of the CSS when it's relatively tiny compared to images.
If I was interviewing someone and they asked what the weather was like at the office, I would just think they'd wasted a question on something they could easily Google.