I have to repeat it over and over for the device to wake up. "Ok Gogle" ... "Ok Gougle"... "Ok Goo gle"...
I really wish you could change it.
5,930 karma · joined June 26, 2013
(English is my second language. So I may make stupid grammar mistakes.)
———
• Full-stack web developer @ http://robotshop.com/
• Opinions are my own and not the views of my employer
• raphael AT-AT raphmedia DOT com
• topcolor: 50b1db
———
I have to repeat it over and over for the device to wake up. "Ok Gogle" ... "Ok Gougle"... "Ok Goo gle"...
I really wish you could change it.
There is nothing stopping anyone that has an e-commerce website from recording a clear version of your passwords along with all of your billing address and credit card informations.
There's no audits or anything.
The only exceptions being the super generators which are pages where multiples sound generators are mixed together on the same page.
Edit: It was confusing how this message is under the myNoise discussion thread. The parent comment of my answer was talking about Brain.fm
Oh wow. They didn't kid around when they said "7. Watch your life fall to pieces."
I got dizzy from all the options out there so I spent some time improving my knowledge of JavaScript itself instead of focusing on someone else's library.
In the end, those frameworks are "nothing" but a lot of JavaScript patterns stuck together.
Switching from one framework to another should't cause THAT much friction.
Edit:
Interesting that this comment is being downvoted. Initial page loading time is not a nitpick, it is the main source of an increased bounce rates.
> "[Users] with an average page load time of 2 seconds view 8.9 pages on average, while those with an average page load time of 7 seconds view only 3.7 pages on average. The number of pages viewed consistently decreases as page speed decreases, and the difference in pages viewed between users averaging 2 second load times and users averaging 4 seconds is 3.x pages. This means that a 2 second delay in page load time could mean a user exits your site 3 pages earlier."¹
Articles upon articles are written on the topic and UI/UX experts have a lot of patterns available to mitigate the issue.
This article showcases a lot of great way one can use to change the perception of a slow loading page: https://medium.com/dev-channel/hacking-user-perception-to-ma...
---
¹ https://blog.littledata.io/2017/04/07/how-does-page-load-spe...
The law asks one to "act faithfully". Faithfully can easily be used as a synonym for devoted and some employers ask a religious devotion to the company.
| 2088. The employee is bound not only to perform his work with prudence and diligence, but also to act faithfully and honestly and not use any confidential information he obtains in the performance or in the course of his work.
| These obligations continue for a reasonable time after the contract terminates and permanently where the information concerns the reputation and privacy of others.
He concluded with some really good points:
| I came away from the experience unable to commit myself to a company. In part this was an ethical stance: who controls the company can change, and change quickly. So loyalty to a company meant committing to follow people who shouldn't be followed, not because authority is inherently bad, but because in most companies authority cannot be rescinded by the workers in its power.
| But it was also an emotional reaction: I'd put a lot of myself into my job, only to see my work—and my friends' work—destroyed in an incompetent power grab. I didn't want to go through that again.
| The thing about loyalty, though, is that it's motivating: you give your loyalty because you want something or someone to succeed. So if you're past the point of pure survival, where do you find motivation if not in loyalty?
| Eventually I came round to solidarity, a thornier path than loyalty. Loyalty is simple, because it starts with an answer: your country, your cause, your company, your friends—above all. Solidarity is complex, because it starts with a question: beyond yourself, beyond your friends, beyond your cause, beyond your country, what ought you do to help everyone?
They are very popular on HN because the main users here are not front-end engineers or designers. They are hackers who want a quick landing page for their project. Those quick and dirty frameworks are perfect for it.
To be honest, we are actively hacking our body when using hormone replacement therapy. Strange things are bound to happen. Skipping a dose of estrogen can trick the body into triggering PMS like symptoms, etc.
That being said, I've not given money to an homeless person in ages. Whenever asked I simply answer "I only carry cards, sorry" and they immediately lose all attention towards me.
What I've lived through a lot of time is teams of senior programmers led by junior managers. Sometimes they are fresh out of school and have never led any team. Heck, sometimes senior programmers turn into code monkeys because they are hired as nothing more than glorified trophies. IT teams having to answer directly to sales department managers, etc.
Teams of juniors or intermediates are way more likely to make mistakes such as the one you describe. I've seen my share and I do agree that they exist. People migrating entire projects to the language-du-jour and creating a bad situation for everyone because they didn't master that language and ended up refactoring stable solutions into shaky messes.
In a perfect world, we would have a team of strong senior programmers leading a few juniors under a strong management team.
What always ends up happening because of this is that managers start to manage time spent instead of value outputted. Since the work done is all very vague for them, the best programmer is the one that finish their projects the fastest.
We do our own estimates and our subconscious is trying to "win" that race. Sometimes, we even get bonuses based on this. So we end up stamping time estimates that would only happen in a perfect world. Management use those estimates as hard deadlines. If you do not meet the deadline, it's your fault.
So you start to work crunch time at the end of months.
Since the work is virtual, nobody but the programmer cares about the quality of the work. Management pushes you to finish as quickly as possible.
You then start to work for free one or two extra hours a day every day to fix those things in the code that bring you shame.
The things management won't give you extra time to correct. You know this glaring security hole is going to end your career, even if management doesn't want you to correct it. So you correct it anyway.
You want better tools to insure the quality of your projects but since programmers have to build their own tools from scratch, management won't grant you time to build them.
You use some time out of your weekend to build them.
Nobody wants to use a dull blade so your sharpen your tools on your own time.
A few projects done the road, you work 20 extra hours a week without even noticing anything has changed.
... now imagine a new hire trying to compete without putting any extra time. On his first meeting, he gets asked why he takes double the time to finish projects. He quickly end up doing the same as everyone else. Everyone is working for free because everyone else is.
It's a vicious circle that's very hard to break. Most of the time you only notice it when you are a new hire... and nobody listens to new hire. Heck, what management would allow the situation to get back to normal? They are getting so much free work.
I prefer to use SASS variables along with a strict build system that refused to build if the developer isn't using variables that are injected via a config YAML file. In the end, we are both working in a similar way.
That being said, ".u-colorPrimary" is great. You can easily refactor it and it should scale well. However, ".bg-orange" and ".text-white" aren't great.
This button from the article is really bad:
<a class="text-xl rounded bg-orange pt-1 pb-1 pr-4 pl-4 text-white hover:text-white no-underline leading-loose" href="#">
They should at the very least made a component with the styles and then apply via ".button" class.On a small one page website, do use them. However in something more complex like an e-commerce website theme or a complex web app, you will regret it quickly.
<a class="text-xl rounded bg-orange pt-1 pb-1 pr-4 pl-4 text-white hover:text-white no-underline leading-loose" href="#">
is no better than
<a style="font-size:16px; border-radius:5px; background:orange; color: white; text-decoration: none;" href="#">
It is simply a fancy way to use inline styles.
One of the selling points of CSS is the ability to scale and refactor very quickly and easily. Class based frameworks remove all those benefits. Extracting components and building sementically is the solution. As I said in my previous comment, that framework they are using supports it. They say it themselves:
“*While we strongly believe you can get a lot further with just utilities than you might initially expect, we don't believe that a dogmatic utility-only approach is the best way to write CSS.*”
I have worked on many contracts where the client came to us because their current web agency wanted to charge crazy prices to refresh their website's design (e-commerce websites change at least one a year). Almost every time, those projects are a pain for both the team and the client because the previous developer decided to be lazy and use classes or inline styles everywhere.Look at the button from his article:
<a class="text-xl rounded bg-orange pt-1 pb-1 pr-4 pl-4 text-white hover:text-white no-underline leading-loose" href="#">Buy for $10</a>
That's way too granular.
Even the framework that they are using proposes better alternatives.
“Tailwind encourages a "utility-first" workflow, where new designs are initially implemented using only utility classes to avoid premature abstraction.
While we strongly believe you can get a lot further with just utilities than you might initially expect, we don't believe that a dogmatic utility-only approach is the best way to write CSS.”
Read this page: https://tailwindcss.com/docs/extracting-components/
A class based rapid prototyping framework is a powerful tool, don't get me wrong. However, like all tools you should only use them when they truly are needed.
When I write CSS, I use a lot of shortcuts. I simply write "mt5" and then press tab, it then auto completes to "margin-top: 5px;". If I write "tdu"+tab and then it goes "text-decoration: underline;". The IDE also shows me in a drop down all the options that can be used after writing "text-decoration".
Changing standards because you do not want to learn or remember something is the perfect example of programmer "laziness". Why remember this super common language when instead I can develop and remember a new obscure abstraction instead?
When done properly and with responsibility, it does not claim any accuracy when it comes to telling the future.
It's a tool that you use to have deep and meaningful conversations. The cards are loosely similar to Jung's archetypes, among other things. Modern tarot is an anachronistic melting pot of many philosophies and concepts.
You simply use the cards to investigate a situation. You may discover someone's fears or hopes through one of those conversations. You can then use this information to help them plan out their future. That's pretty much it.
---
For example:
Say someone asks you about their career and you pick a card that means "shyness" at some point. The conversation then focus on the concept of being shy. Is this person shy? Could their shyness be the thing that make their work life harder?
If the answer is no, do they have someone at work that may be shy? You then talk about that.
If the answer is still no, could it be that they should be more shy? Is this person too bold? You ask this and the person gets defensive about themselves. A good reader will be able to notice this and then shift the conversation on that.
Through this discussion, they tell you that they might be too brash about one of their employees. You can then help them figure out a plan for the future, a plan to apologize or simply be more emphatic about that employee. But this person come up with the plan by themselves. You simply facilitated this discovery.
---
In short, it's a tool that get people to open up to you. Some people abuse of this. They give dates, prophecies, claim truths. They pick up on the points where the person they read for gets defensive and then use this information to emotionally blackmail them.
A good tarot reader is a good listener. You should not make any claim, you are not a trained therapist. Tarot readers should allow people to discover themselves without forcing anything. They should never say "you are x and need to do y before z happens".
(This is going to be controversial on HN. Keep an open mind and be polite. I am not a professional tarot reader and decline reading for people most of the time because of the liabilities that come with it.)