proexploit
Joined 17 years ago
Joined 17 years ago
`::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.
It's not that the stuff you would do isn't relevant to starting your business but that it's not the complete picture.
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)
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.
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.
That's also not what the parent comment I commented on was referring to.
(I don't know if that's a formal guarantee but it's my experience)