VirtualTam's bookmarks
-
- Discussion on Hacker News
- Book report by Steward Brand
- ROMchip Presents: Building SimCity: A Conversation with Will Wright and Chaim Gingold
- EA Sim City 2000 Will Wright Interview
- Game Developer Magazine - April/May 1995
- Stanford Libraries - Interfacing to Microworlds, Will Wright, Maxis
- Will Wright on Designing User Interfaces to Simulation Games (1996) (2023 Video Update)
- Will Wright and Brian Eno - Generative Systems
- Playing with Time | Brian Eno and Will Wright
- SimHacker/MicropolisCore - SimCity/Micropolis C++ Core
Related books:
-
2023-10-29 Grumpy Website is a world-leading media conglomerate of renowned experts in UIs, UX and TVs.
We’ve been reporting on infinite scrolls, cookie banners and unnecessary modal dialogs since 2017.
-
2022-09-04 -
2019-09-24 -
- Unicode text segmentation - https://unicode.org/reports/tr29/
- Unicode emoji - https://unicode.org/reports/tr51/#Searching
- https://jolicode.com/blog/search-for-emoji-with-elasticsearch
-
2017-12-21 -
https://blog.returnpath.com/how-to-explain-dmarc-in-plain-english/
-
https://blog.returnpath.com/infographic-how-to-prevent-email-fraud-with-dmarc/
-
https://blog.returnpath.com/build-your-dmarc-record-in-15-minutes-v2/
-
https://blog.returnpath.com/how-to-read-your-first-dmarc-reports-part-1/
-
https://blog.returnpath.com/how-to-read-your-first-dmarc-reports-part-2/
-
https://webmasters.stackexchange.com/questions/102509/dmarc-understanding-aggregate-reports
-
https://webmasters.stackexchange.com/questions/90326/dmarc-spf-fail-dkim-pass-source-ip-not-mine
-
https://www.endpoint.com/blog/2014/04/15/spf-dkim-and-dmarc-brief-explanation
-
https://stackoverflow.com/questions/30342550/why-do-i-receive-a-dmarc-report-everyday
-
-
2017-12-21 - https://dmarc.org/resources/code-and-libraries/
- https://blog.returnpath.com/how-to-read-your-first-dmarc-reports-part-1/
- https://domainaware.github.io/checkdmarc/
- https://github.com/domainaware/checkdmarc
- https://github.com/domainaware/parsedmarc
- https://github.com/trailofbits/dmarc
- https://github.com/beckspaced/Dmarc-Report-Viewer-Extended
- https://github.com/linkedin/lafayette/
- https://github.com/thinkingserious/sendgrid-python-dmarc-parser
- https://github.com/prbinu/dmarc-report-processor
- https://github.com/alan-hicks/django-dmarc
- https://github.com/martinhoefling/go-dmarc-report
- https://github.com/cheatas/DMARCate
-
2017-08-22 With so many interacting components, the number of things that can go wrong in a distributed system is enormous. You’ll never be able to prevent all possible failure modes, but you can identify many of the weaknesses in your system before they’re triggered by these events. This report introduces you to Chaos Engineering, a method of experimenting on infrastructure that lets you expose weaknesses before they become a real problem.
-
2016-08-16 - Understand user needs
- Do ongoing user research
- Have a multidisciplinary team
- Use agile methods
- Iterate and improve frequently
- Evaluate tools and systems
- Understand security and privacy issues
- Make all new source code open
- Use open standards and common platforms
- Test the end-to-end service
- Make a plan for being offline
- Make sure users succeed first time
- Make the user experience consistent with GOV.UK
- Encourage everyone to use the digital service
- Collect performance data
- Identify performance indicators
- Report performance data on the Performance Platform
- Test with the minister
-
2016-03-21 -
2015-02-13 Python's built-in unittest module is quite cool, but a bit limited and way too verbose (read: it's quite not easy to incite developers to write unit tests)
I'm currently looking for more dev-friendly solutions, the key points being:
- writing test code should be easy and straight-forward -keep the focus on "what to test" instead of "how to transcribe a process to a test"
- parallelization! -we, spoiled developers, should make good use of our way-too-many-cores build machines...
- complete feature set!
- we don't want to just run tests...
- coverage reports (find dead/weak/untested code sections)
- output formatting (JUnit-XML seems to be quite a common format out there)
There seem to be 3 solutions in Python:
- stock unittest + project-dependent customizations / test helpers
- nosetests
- py.test
And 2 ways of gettings things done:
- keeping things stock: no external dependency, project-specific implementation...
- using a test framework: one more module in your (test) virtualenv, more concise tests, more features (// run, code coverage, etc.)
Some links:
-
2014-12-31 -
2014-12-20