161 karma · joined October 30, 2018
They said that about radio. They said that about TV. They said that about computers. They said that about dumbphones. They said that about smartphones. They're now saying that about apps.
https://www.theguardian.com/money/2019/nov/02/after-grenfell...
So you pay zero on the first £12,570 of earnings. Basic rate of 20% from £12,571 to £50,270 of earnings. And then 40% on £50,271 onwards.
(We have additional rate over £150,000 of 45%).
It's important to remember you don't pay a flat %age on your income. It's worked out as a precentage of income you earn inside the thresholds
https://en.wikipedia.org/wiki/List_of_European_countries_by_...
Though I suspect both yourself and the previous poster was referring to the European Union.
Can't just buy a gpu and plug it into a wall outlet.
[0] https://www.itjobswatch.co.uk/jobs/london/senior%20developer...
Everything from the price of broadband, pint of milk, loaf of bread, healthcare, car costs, etc etc contributes to someones buying power vs their salary
Think about the problem horses/cars were solving. It's clear people 'wanted' that problem being solved just by how prevalent horse-as-utility were.
"I see your [bet] and raise you [x]" - would that be accepted?
When do you see friends? When do you exercise? When do you go out to eat? Watch a film? Play video games?
Seems like that entire routine is about maximising your time working.
I'd rather be somewhat inefficient at work if it means I can have a balance which means I enjoy my life.
The way these work is by tracking other moving objects around you rather than stationary objects you are approaching.
It'll track another car to see if it emergency brakes or changes lane too close to you, but it won't track a parked car on the road that you side swipe or head into etc.
I figure after 2 in a row, the next place has got to be step backward a good 5-10 years. I'm putting it off as long as possible.
Though saying that the first place I worked was firmly stuck in the 1970s so maybe I got it all out the way in those first 3 years.
Whos winning? Arsenal are (team)
Whos winning? Ronnie O'Sullivan is (singular)
Disclosure: I am English.
Both great examples of trademark erosion, tbh.
- I can't adjust the volume without looking at it. Because the touchbar is flat with no haptic feedback when I land on a button, it's hard to remember the exact position of the volume 'button' without looking. Sounds trivial - but combined with point 2....
- The way the volume control expands - it actually moves the 'volume down' button AWAY from your finger, which again requires me to keep looking at the control.
This means that when a loud song comes on, it can take 2-3 seconds to quickly turn the volume down in total. I could do that with one single keypress in half a second or less on a keyboard, without needing to look at the keyboard.
That can also be the difference between missing a key detail from a quiet speaker on a Hangout.
Flashy, but it's a terrible user experience by every metric other than looks, I guess.
The textures and subtle tones, the method of craft, the interplay between mixed media, the energy (or lack of), the emotion (or lack of) etc and so on.
All of that gets lost in a 512x512px image.
This attitude is reflected in their homes, also. (I'm talking about sub-urban or rural, not metropolitan) They tend to build their homes to last around 20-30 years, then they'll knock them down and rebuild them. But they would still refer to it as the same family home for [x] decades.
source: https://www.theguardian.com/cities/2017/nov/16/japan-reusabl...
This is true. It is also the worst piece of hostile-UX I've ever seen. I'd love to have seen the Product Designer and Product Manager tie this one back to revenue forecasts. Who knows, maybe its a huge converter?
It just seems overly hostile to me, as if thats the only way they could think to increase revenue - instead of, you know, working on their core value proposition.
If your cross functional team (Product, UX/Design, Eng) are aligned, it doesn't matter if you build the wrong thing initially, because you'll follow a good agile and/or lean process to validate early and thus learn what you should be building earlier.
It's not saying 'being aligned is more important that building valuable things' - but "if you focus on building a team that functions well operationally and strategically, you'll figure out how to build the right thing quicker".
When it's work best anecdotally, is when we hold regular retrospectives ON our agile ways of working. EG: Is the standup working for us? What should we stop/start/continue in our standups?
When this 'retro of agile' (rather than just project/product retros) take place regularly you quickly come across a format and cadence that works for the team.
Tools are just tools, they should work for us, not the other way around.
So for example, if you would pen an email/slack talking about a slide deck from a recent meeting, in the widget the product would have already found the deck ready for you to drag and drop it into the message.
It worked freakishly good, and saved a whole bunch of time trying to find a file in the mess that everyones Google Drive becomes.
The problem they were having was no enterprise wanted to hand over an entire copy of their data for them to index.
Usability and interaction design is most certainly part of UX. However, the skills needed to be a competent visual designer match (in terms of difficulty, time to execute, etc) that of being a UX designer. Simply put, in order to go deep enough on either craft, you need to dedicate to one side or another.
There are many dual 'UX/UI' roles out there, but they tend to be weighted toward the UI side, maybe with some user testing tacked on the end or some journey work.
Sole UX roles are much deeper in their reach within an organisation and consist of much, much more than just wireframing and making visual deliverables.
For example:
Two competing microservices? One has a spin up time of 0.3 secs, the other 1 sec. The first is two times the price. It is the job of the UX designer to understand the impact of the longer spin up time to understand if it would impact the user experience.
The UX designer then works with the Product Manager to build a business case for the correct service and thus you've made a decision that impacts the UX but is not a UI or interaction based conversation.