It's not replaced, it's in addition to the text. The HTML gives you one copy in black, then ::before & ::after are used to create copies in red and lime green. Partially showing those copies is what give you the glitch effect.
`::before & ::after` are pseudo-elements and a very common way of creating independently styleable elements when doing CSS effects like this
`content` is a property you can use to add text to those elements (he could have also just written `content: 'Artificial Truth';` if he preferred - having it as a data-attribute puts it right next to the "real" text and makes things easier to maintain)
`attr(data-text)` sets the value of content to the value of an attribute of the HTML. data-* is a common convention for creating value that aren't used for display. It is not possible, to my knowledge, to access the text contained within the `<h1>` with CSS only, hence the above choices.
They're definitely related (and more so the closer to start a business is). Depending on the business you may be benefiting from research, product/market fit, marketing, experiments, and on and on.
It's not that the stuff you would do isn't relevant to starting your business but that it's not the complete picture.
I think it's a lot harder to pick a good business than you think. Many "micro" sized businesses have significant issues and avoiding them requires you to know all the right questions to ask.
If you are able to make the right pick and the size of the deal is something you're comfortable seeing go to zero, it may be a good learning experience.
However, you'll be learning to acquire and keep a business alive, not start a business through this. Some things may remain the same depending on the stage of the business but if you're looking for experience starting a business, I think starting on and failing will be better training (and free)
I've worked at Google as a UX Engineer and really enjoyed the role. It's closer to coding than design but if you have strong design skills that may be something you can choose to do differently.
My job was best described as a prototyper specifically. Embedded in a UX team, I worked on prototypes of new features, prototypes for new research and internal tools to assist the UX team (for example, better visual design and motion specification for engineers).
My take was also that non-FAANG companies don't often have enough prototyping work for a full time prototyper so this is a role that's most often seen in large organizations.
Other than that, you won't see a lot of the role. If you're a designer and developer, you've spent time learning both disciplines. Many who have focused just on one discipline may have a greater skillset purely due to time spent learning and executing.
At the end of the day it all comes to down to the individual and the specific team. As a PM now, I greatly value engineers with an eye for UX and designers with an understanding of code which would make me more likely to hire you but the role would still be just for an engineer or a designer.
The emphasis of any one element detracts from the others. In many websites, emphasizing the signup button is achieved by de-emphasizing the login button.
Imagine a page with 100 highly visible buttons. It would be extremely difficult to determine which one is likely to be the important action you want at a glance. The same principle applies with 2 buttons, just to a lesser extent.
Your personal example seems simple enough, the other 2 seem like massive undertakings for one person though. I'm sure they started simpler. Are you willing to share any profit or traffic stats about your site?
But your application could store them there... I don't think the use case most users are looking for is to have a magic Drive folder that automatically processes purchase orders when they're added.
That's also not what the parent comment I commented on was referring to.
Actually yes. You're emailed a receipt with a map that includes the route you took. If you have any complaints, you can email them and they'll usually adjust your rate.
(I don't know if that's a formal guarantee but it's my experience)
And force the developer of every app to do two complete themes (assuming they have some branding / color scheme)? While I agree it would be nice if everyone did have the option, I don't think it makes sense as a requirement.
This is the impression I got as well. Stripe's policy seems to agree to export the cards but that doesn't mean you can pick any format and requirements you want and they have to follow them.
Chase needs the cards in a specific way but without more information it's hard to make the claim that's the only way acceptable by law.
If Stripe is unwilling to do extra work with Chase to get cards exported, that doesn't seem to be "refusing to transfer credit cards to another merchant per their policy".
Can you provide some more information on what part of the transfer they object too?
> Of course, it's possible more companies have challenged this secret surveillance, but we just don't know about it yet.
And no other mention of Google in the article. Great that Yahoo fought them but it doesn't support your assertion that Google immediately gave in or cares less for privacy than Yahoo.
Even better, the same source you provided (EFF's Who Has Your Back report: https://www.eff.org/who-has-your-back-2013) gives this as Yahoo's only positive mark while Google is 5/6.
> Yahoo is definitely not good on privacy, but at least they fought as hard as they could before their hand was forced where google capitulated immediately.
`::before & ::after` are pseudo-elements and a very common way of creating independently styleable elements when doing CSS effects like this
`content` is a property you can use to add text to those elements (he could have also just written `content: 'Artificial Truth';` if he preferred - having it as a data-attribute puts it right next to the "real" text and makes things easier to maintain)
`attr(data-text)` sets the value of content to the value of an attribute of the HTML. data-* is a common convention for creating value that aren't used for display. It is not possible, to my knowledge, to access the text contained within the `<h1>` with CSS only, hence the above choices.