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.
That makes sense! Your explanation on why using the data attribute can enable more advance trickery just clicked multiple things in my brain when remembering other fancy codepens.
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)
Yeah I expect this. I think I would like to start from something I am somewhat familiar with.
Interesting note about "acquiring and keeping a business alive, not starting a business", I am under the impression that these two skills are related, if not the same.
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'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?
Posted on Reddit twice, (first initial spike once I finished it, second spike when I added more of the cases.) That's about the extent. Got me all the Google-juice I need to ride it out.
Total work probably around... 40 hours, at most. I stopped supporting it in 2014. HTML + Canvas. Used images hosted by VALVe instead of hosting my own. Never had the motivation to make it better. Hosting was provided for free by a friend.
Was at the top of Google for a while. Got knocked down by a much more active developer (which is monetized even better than mine.) I only display 1 banner ad instead of an aggressive 3. I didn't improve it at all since then. However, I feel I had a technical advantage over the Flash-based competitor, as mine ran great on mobile. I assume the competitor has since improved that aspect of theirs.
I get ~$100 payout every 4 months now (~$25 per month)
Spikes in January 2015 and Sept 2015 coincide with new CS:GO game updates. They added new cases to the game, which I never got around to implementing in the simulator. No doubt missed opportunities.
Things I could've done better:
- Actually keep working on it. (New cases, new features, better backend, trade-up simulator)
- Better monetization (Only 1 banner ad, when Google allows 3 on one page)
What went right:
- First person on the playing field. (Still was delayed, since cases were released in Aug 2013 and I released it on March 2014)
On the subject of the others: They're just aggregating data about the game. You can start with the smallest, easiest bit and slowly build up from it.
For Wowhead it was: Aggregate item data. Then quests. Then zones w/ maps. Resource spawn points. Raid information and guides. Etc. etc. They were one of the first information providers for World of Warcraft and then they got acquired by Curse.
In the case of the Ark calculator, it started as: "This algorithm in the game is mysterious to players, I'll recreate it in the browser." Then they added stuff like "this Dino destroys X stuff", "this Dino can do Y"
> The Google Drive API includes a special hidden folder that your app can use to store application data.
Again, that means a user cannot drop their files into a special app folder for processing. It does not facilitate the simple use case of creating an App to distribute purchase orders to vendors.
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.
I think it is a very common use case to have a folder for an app that will do something and not have an app need permission to your entire folder. But google doesn't think so. You had responded to my comment which talked about such a use case.
I think it is obvious that purchase orders are an example. Have temporary hidden storage via an application data folder may be useful, but I am talking about folder level permissions for an app.
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)
Also you generally enter your destination into your phone before ever getting in the car. The company usually knows which account holder is riding, who is driving, which car, and where they're all going at the time the ride begins.
The most prominent, composing a new email. The floating window appears out of bounds and it's impossible to click any buttons on the lower bar, including the send button.
What I do is tabbing all the way down so the floating window reorganizes allowing me to send the email.
`::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.