It's wild how many of these so-called sabotage techniques happen daily in the workspace without even realizing it. I can’t tell if this website is being serious or just having a laugh. I don't know whether I find it funny or sad.
Is this a deep philosophical reflection on the nature of work and organisational behaviour?
Or does it simply reflect the fact a good sabotage technique is something you can get away with - and therefore it has to be something that happens daily in the workplace?
That is, in fact, the point. You don't want to get caught/fired for sabotaging your company. The site suggests introducing additional perfectly explainable events which happen all the time, and are hard to assign blame to direct incompetence, but slow progress and cost money.
* Adopt a colour scheme with similarity to the old BOM?
* Some way to store longer baseline movie animations in local state so people can avoid cost in you but run the weather radar for longer?
* Tide info? Hyper specific to people who do water things. Willyweather does this really well.
I use Willyweather and Windy. I used to use a weather app written by some mob called "shifty jelly" and their git logs were .. hysterical. Drunk fairy penguins seemed to cause most of the bugs.
Dataviz suggestions from top of the page to the bottom:
- Location search & display: no English version, only localized names, which is hard to reason if you don't know native language.
- Summary: a) what does precip. in % mean and how it correlates with cm? b) pressure is only displayed in hPa, while some countries prefer mmHg; c) what does ozone index mean and why is it important?
- Next 24 hours: visual indication for temp variation through the day would be easier to reason than just by looking at numbers (as discussed in TFA).
- Next 7 days:
a) unnecessary precision for y-axis (e.g. 10.9°C vs. 11°C);
b) band overshoot actual values (e.g. if I see 10..−10°C, I assume that would be max/min temp, but in fact it is 8..−9°C, which is impossible to tell without hovering mouse over);
c) no horiz. line through 0°C;
d) no horiz. lines through y-axis ticks, which makes it harder to reason about values closer to the end of the graph;
e) precip. in cm tells little, especially when band is alike (0.00..0.80 cm) - peaks on graphs look like a lot, in fact they are not? g) seeing blue precip. graph subconsciously means 'rain' to me, while in fact it would be snow;
f) labels for y-axis are at the same time very small, rotated 90° and also take too much horizontal space from the graph.
- Map: moving mouse over next 7 days graph causes time shown on map to change that would make sense if map's timeline would cover all 7 days, but it only covers small part of today.
- Week:
a) fog icons look like they have solid white square background, which seems to be off compared to other icons;
b) low/high values are hard to reason about, especially when it says 'Low … at 11am' and there is no tick labeled '11am' (10am .. 12pm) - displaying a line through coldest/warmest hours with °C value next to it would be much easier to understand.
Also: displaying air quality prediction based on last year's AQ would be helpful.
Could you tell me the significance of the location in Australia that's used by default? I frequently clear browser cookies and history so it often jumps back there, so I see that location a lot, but can never envision exactly why it was the default. (Specifically, a point along Gol Gol Road in Arumpo, NSW, Australia.)
This is neat, but I find the charts extremely hard to parse due to the color gradients and the similar shades, especially of blue and teal. I find the Merry Sky charts a lot easier to understand.
Thanks for the feedback. You helped make my app more readable (I went a little overboard on the gradients; I thought the gradients would help convey the sky condition):
- Also added shadow/glow to plot lines so they "pop out" more.
I'm not sure which parts you think are blue and teal. Open to suggestions for better colors! (There are only so many colors, and I like keeping the precipitation related colors all bluish.)
You mean you prefer C over F? Tapping any temperature will toggle between the two. (This always comes up, so the app should probably default to units based on the user's location: the default is F only if the app detects you're in the US)
- Toggling C/F also toggles the scale on the radar to km. Eventually, I will get around to adding a dedicated settings page.
- However, the app was designed so one could get a sense of the weather without numeric labels: temperature is a very relative experience, so use the spatial/color cues to compare yesterday, today, and forecast days.
- Notice now much more space C needs when toggling between C and F. F's 0 to 99 range fits the natural range of temperatures humans experience (weather, body temperature). Humans just don't experience anything beyond 50 degrees C. At the same time, a single delta C is too large for the precision human bodies can detect. (Humans need something closer to 0.5C precision, which is what 1 degree F is.)
- As as result C needs nearly twice as much horizontal space compared to F: due to going negative more often and needing an extra decimal for minimal precision required.
I'd sneak in 'Toggle C/F' somewhere and hook it to the same function you use on the numbers.
Fahrenheit goes negative at a measly -18C. Where I live -20 to -30C is not uncommon. Whether it's 17.5 or 18C typically does not matter, continual changes in wind and other factors will for pretty much all practical purposes quench that difference.
As a windsurfer, wingfoiler, and kitesurfer i can only say that both Windy.app a nd Windy.com are awesome. Like the ability to compare different models easily.
I'm appalled by how little media coverage this topic is getting in Canada right now. Hopefully, journalists and citizens will pick this up, and the bill will be defeated.
Not everything in life needs to be optimized with some system. Just politely wave at your waiter, wait for them, or pay at the cashier near the exit if you're in a hurry. Talk to people. Embrace the little chaos of life and the small imperfections that come with it.
It's either that, or get denied. Interestingly enough, however, it's quite easy to "prepare" for a phone search in advance since border agents can only search the actual content of your phone. You just need to delete apps and reinstall them after you passed the border. Their "advanced" forensics tools would likely find traces of those deleted apps, though.
"CBP officers can only search and access data stored on the device’s hard drive or operating system. The search does not include data that is stored remotely in a Cloud format. The officer must ensure that data and network connections are disabled before starting the search, for example, by asking the traveler to turn the device into airplane mode and disabling Wi-Fi."
This resonates with my experience. The consulting/software company I work for practices price transparency (even though we're the most expensive in our market) and pushes hard for email communication with leads and clients. Our stuff is heavily documented. More substance, less BS.
We used to do lots of sales calls years ago, but 99% of our entreprise growth came from being active members of our community and talking (email!) to engineers. We still do sales calls, but they're essentially what the author calls "discovery calls". And we prequalify the shit out of leads before we take a call with them -- yes, that means taking a few minutes to learn about what they do.
reply