"Rather than using fallbacks and shims to ensure a design and layout look the same across all browsers, we’d provide the mobile vertical single-column layout to all browsers and then serve up advanced functionality to those browsers and viewport widths that can take advantage of them."
+1 This is a great solution that doesn't take a huge amount of time to implement. Esp if you only use CSS Grid for 2d layouts and use flex for which has decent IE11 support for laying out components (where mobile is often just stacked 100% width components).
A good way to bring a client round is to explain that the time saved on making IE11 pixel perfect is better spent adding features elsewhere.
We support Grid by default.
If Autoprefixer see that your CSS is too complicated for IE, it will warn you to disable Grid support and use some JS polyfill.
Parents would have to be equipped to be able to answer these questions in the way you suggest though. That seems a bit of a stretch if they haven't been educated similarly themselves
a similar scam has been going on for a while, with at least video games, board games, and bike gear, from what I've seen on Amazon Canada.
Third party sellers with a "real" looking name will list an item at a ridiculous discount off retail. If you buy it, you get a Chinese international tracking number. This takes forever to "arrive" and it turns out Amazon only really cares that the tracking number shows to Canada. I'm not sure what is actually in the package, since it's not possible to figure out more than just the city it went to.
Eventually, Amazon will refund you, but it's a bit annoying. It's pretty easy to spot once you get bit the first time, but you'll usually see the third party seller spike to several hundred bad reviews before the entire situation gets resolved.
This seems like Amazon CSR just failed to read the writer's complaints correctly. It should eventually get fixed, because it often does get fixed, even for hundreds of customers at a time.
This happens with books too, though in these cases it can be more difficult to spot beforehand (e.g. 20-30% off a cover price isn't too unusual). However, if the seller has _every_ book listed for the same price, something is very obviously wrong.
From those I've seen, it looks as though old and/or inactive accounts have been compromised. These have a decent history, possibly even a positive feedback rating, but no activity in (e.g.) the past 12 months.
on .ca they seem to be newer accounts, often "FIRSTNAME LASTNAME" "located" in the US somewhere.
Totally forgot the _every_ book thing - they also sometimes have items that aren't actually released yet, but are available for immediate shipping, which I guess gets them bumped up a bit.
It was mostly persistence and luck in finding a position that matched my existing skills and interests. You'll often have a code screen as an early step (because remote jobs get hundreds of applicants in days), so getting good at those sort of problems can be helpful as well.
It's even more fun, in BC "high technology companies/professionals" are exempt from a bunch of the usual labour laws around overtime, hours of work, stat holidays, etc.
PolicyStat | Carmel, Indiana or remote | full-time (remote)
A hospital’s best tool for standardizing and implementing life-saving improvements are their written policies and procedures. PolicyStat’s mission is to improve healthcare delivery by making those policies and procedures easier to find, access, and enhance. Our clients (across 46/50 states) use our SaaS application to ensure that this critical information is correct, their staff can find it, and that it supports regulatory compliance.
In this role as our 5th engineer, an experienced software engineering generalist, you will be a critical part of our engineering team. You will spend time on all aspects related to delivering a great web application to our users. We're a small team, so you'll sometimes be asked to wear hats ranging from API design to algorithms and libraries to front-end engineering. We’ve recently been freed from the tyranny of supporting Old IE, and we’re excited for the opportunity to improve interaction for the hundreds of thousands of people that rely on PolicyStat.
We are a remote-friendly team, currently with members in Indianapolis, Vancouver, Brasov, Barcelona, and elsewhere.
Our interview process is mainly work sample based: one short screening work sample, human interviews, then a 3-4 hour work sample using our tech stack. No whiteboarding involved.
This is a great post. I think the "paid to write code" is often a byproduct of environment - whether it's poor engineering leadership, bad productivity measurement, etc.
A follow up to this, how do benefits work for team members who are not in the USA? I imagine things like health insurance would be different, for example
I've seen fallback CSS and JavaScript polyfills used.