Photographing before I frog the lot. I fear there is something structurally wrong with my design. So let’s frog and start again for the third time on this project ::sigh::

seen from United States
seen from United States

seen from United States

seen from Singapore
seen from United Kingdom
seen from Spain

seen from Israel
seen from China
seen from Yemen
seen from India
seen from United States
seen from United States
seen from United States
seen from Germany

seen from Germany
seen from United States
seen from United States

seen from Malaysia

seen from India
seen from Australia
Photographing before I frog the lot. I fear there is something structurally wrong with my design. So let’s frog and start again for the third time on this project ::sigh::
So there's this playground, i wonder what's the target age for it?
This is quite steep for a little kid. So i was wondering is this supposed to be deeper in the ground (like all those metal poles sticking out from beneath the wood). I get one would want to have some protection for the wood, the wet ground would make the wood rot eventually, but couldn't it be further in the ground?
So basically like this (excuse the poor artistic rendition)
But this is where we run into another problem....
Where's the slide gonna end if we put the whole thing deeper into the ground? Yeah right, the kids would slide right into the ground, yayyyyy
God i hate this shitty slide
Apparently the people doing communication at Overwatch forgot all their accessibility courses.
Not only they chose the thinness font ever.
But... WHITE ON SKY BLUE ???
White on sky blue.
Who thought it was a good idea?
This schedule is unreadable. Fire this designer. Fire the one who agreed to this.
https://twitter.com/playoverwatch/status/1359559931691638790?s=21
“Nine days left until #BlizzConline and the schedule is here. Mark the ones you don't want to miss!”
I posted this on Tuesday last week, but I am only re-posting because for some reason (as stated in our Canvas chat), the hashtag #GUMPDC620 would not show my other post. (My other post is still up on my tumblr page just to show as reference that I did post before Thursday.)
For our second visual diary assignment, I immediately thought of the Fyre Festival as an example of a wicked design problem. Of course, this was not an every day event, but I thought of this because with this millennial generation, music festivals are quite the events that many attend to and businesses, artists, and more boom from these events across the nation. In Nelson and Stolterman’s book, “The Design Way: Intentional Change in an Unpredictable World - Foundations and Fundamentals of Design Competence,” they address how “by treating a wicked problem as a tame problem, energy and resources are misdirected, resulting in solutions that not only are ineffective, but also can create more difficulty because the approach used is an intervention that is, by necessity, inappropriately conceptualized” (page 17). The reason I bring this up is because Billy McFarland, the founder of this failed music festival, did not appropriately conceptualize nor did he realistically address the needs and design of a properly working music festival. As they continued their false marketing and other fraudulent activities, more problems came up which only further more wicked design problems. On top of that, according to Netflix’ movie, Fyre, their timeline was unrealistic and off, and they did not appropriately formulate the products and operations behind the festival. As the book shares, one of the main characteristics shown was that “every problem is a symptom of another problem.”
Two of the costliest fighter jets in the world can't talk to each other
Two of the costliest fighter jets in the world can’t talk to each other
Click to enlarge — wired.com ❝ With the F-22 Raptor and the F-35 Lightning II, the U.S. has fielded two of the world’s most sophisticated, maneuverable and stealthy fighter jets. They both function as airborne shepherds of America’s flock of older combat aircraft, using their state-of-the-art systems to communicate threats and targets on the ground and in the air. Unfortunately, they have a…
View On WordPress
mobile: hang
Meta: take out its power
Meta: restart it
mobile: datetime reset to 1980
Meta: unlock it
router: connected to fixed line net link
mobile: connect to router's access point
mobile: can't connect to mobile network
mobile: doesn't sync time using wlan
mobile: (would sync with mobile networks)
Meta: hmm
Meta: browse the repo
Meta: find NTPSync application
Meta: tap to install newest version
mobile: aborts download
mobile: ssl certificate isn't valid until many years in the future :^y
Meta: grargh!!!
Meta: (manually sets correct date with a fictitious approximate time to make the download work.)
at this point it almost seems like tumblr developers is intentionally trying to break the mobile-browser view (though i'm still willing to believe it's incompetence). to wit: 1. the inconvenient placement of a first source only in the notes, loaded separately into a dashboard or tags page, and omitting that in some cases (when directly reblogged from the source?). 2. the bug where some kinds of entries or notifications (mentions?) make a page load as empty on the dashboard. i should probably still report that, it may be new and unintended. 3. immediately preceding entries, those reblogged-from, are no longer shown. (already reported.) 4. the new layout of the "standard view" option (ie, desktop-browser view) breaks horribly now. the top bar must be weirdly positioned, so it moves out of the viewport when zoomed in and is off the side too far where it can't scroll further to the side on that page, making it much more difficult to look at the tracked tags, let alone click on one of those.
oh well. this time, in #test, the test a. entry when edited appeared to keep its position on our dash (listed on dash, before test b.), but again was moved forward in our blog's list view (had been before test b., now found after test b.). apparently tumblr glitches can't even decide on something consistent. (blah blah unknown conditions and proper statistical sampling blah.)