beeswax
Joined 11 years ago
Joined 11 years ago
Once you embrace that pacing (which has been there all the time) you'll be able to appreciate that special kind of game/level design. It seems that Team Sonic was able to apply that principle to Quote a good number of titles with the IP.
Back in the days the controller would have been soaked in several people's sweat ofc and there were no persisted save points. If you want to improve on persistence, priorities and quick decision making: Go play these games on their original hardware (or at least don't use the emulator's snapshot abilities).
In Europe even before 9/11 flight security protocols demanded that a passenger need to be present on the plane and be seated until boarding is complete.
No piece of luggage is allowed to go on the flight if the airline / the pilot / crew / airport staff has knowledge that the passenger is not on that flight: They need to open up the cargo area, remove all containers until they find this person's luggage so it can stay on ground.
Anecdote: When I previewed Kid A via AudioGalaxy back then (it would not be released for another two weeks in my region) I thought the stylistic choices of 'Everything in its right place' were some kind of encoding error (quite frequent back then) so I trashed the whole album after spending hours on the download.
Imagine my surprise when I listened to the album from the physical album I bought a fortnight later :)
Back then we were implementing our own bitmap drawing apps (simply called a PROGRAM back then) in Turbo Pascal (bgi256 ftw). We would challenge each other to come up with faster flood fill algorithms or smaller image file formats.
Good ol' times
I'm currently leading the (soft) transition of a two-platform, not-so-much-shared-code code base (ObjC, Java, Swift, C++) to React Native.
We hit some snags early on (mostly wrt tooling; also prepare to alter your mind set) but as the article states RN yields an astonishing amount of code reuse between platforms as well as heavily reduced turnaround times.
It’s way too early for conclusions/doing a post mortem for our project at this time.
Nonetheless I’d say we’re able to iterate faster by an order of magnitude and the added value of discussing features and domain logic/behavior for both platforms at the same time while enabling UX/UI to get results/feedback faster is a huge win.
That said, I’m really looking forward to the challenges that lie ahead (i18n, RTL quirks, proper unit/feature/integration testing scenarios, non-trivial native bridging, …)
I usually use Disk Inventory X but I'd really like to correlate usage increases to specific dates / app installs, so it'd be nice to see stats over time, e.g:
- Installed Android Studio on Feb 1st: Usage in /Applications increased by 850MB, usage in User folder increased by 10G (450MB for android-studio-2.x.dmg, 8.4GB in /Users/name/.android, largest leaf in /Users/name/.android/sdk etc)
I tried to do this with the 'du' tools once but simply writing the current output to disk would take ages and diffs would need some heavy lifting to make sense of.
I never bothered to measure the intervals, so does anyone know if there's more to it? (the watch has access to heart rate and shows a current rate result afterwards; maybe it's adjusting heart rate goals over time?)
While not actively maintained by Shopify anymore it's working really well, has easy setup and allows you to get up and running quickly.
The grid system and basic widgets provide a good and clean starting point, although you probably want to invest some time to make it visually coherent if you're using a large amount of third-party plugins.
Our team is using it for polled data that is updated once an hour up to every minute and it's working great for us.
Thanks to all of you involved for working on this!
> Just-In-Time compilation (actually Ahead-of-Time)
Also I do like paradoxes :)
95% of all field personell was only able to arrive at the client, sit down and grab a coffee to be talked through some items the first-level support was aware of, while I could actually fix most of the problems due to my deeper understanding of the underlying concepts of the stack (Windows Networking, DNS, SMB, LDAP, SQL, …) right away.
This was the problem: No other engineer was able to see through those things and of course the clients began to notice that I was able to help them way faster; with hourly billing and reduced downtimes this also meant way cheaper.
I was kindly asked to „take my time“ and to „relax, get a coffee first - go flirt with the female office staff“ so my colleagues would not look bad compared to me.
Shortly after I handed in my notice and went for a freelance gig which was the right decision for both the local market and me personally as well (I did not continue with the field service thing but got into custom software development).
http://www-cs-students.stanford.edu/~amitp/game-programming/...