
seen from United States
seen from Belgium
seen from Brazil
seen from United Kingdom

seen from Yemen
seen from United Kingdom
seen from United Kingdom
seen from Indonesia

seen from United Kingdom
seen from United States

seen from Germany

seen from Canada

seen from United States
seen from Belgium

seen from Brazil
seen from Germany

seen from Brazil
seen from Estonia

seen from United States

seen from Russia

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch ⢠No registration required ⢠HD streaming
Just some Harrison gameplayĀ o(ć»_ć»)9
Source āQuickhackā by Dr. Dos (2017) [LD38-QHK.zzt] - āNotesā Play This World Online ---- Discover More Information About This World on the Museum of ZZT
Source āQuickhackā by Dr. Dos (2017) [LD38-QHK.zzt] - āArmory Day 1ā Play This World Online ---- Discover More Information About This World on the Museum of ZZT
Quickhack by Dr. Dos (2017) [LD38-QHK.zzt] - Title screen Download / Explore quickhack-nozzt.zip on the Museum of ZZT Play on Archive.org

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch ⢠No registration required ⢠HD streaming
#quickhack for making #garlic #chutney without any exact measurements- #coconutflakes , #cayenne powder 2-3 cloves of #garlic and salt to taste. Combine in a processor and pulse until combined. #condiment #chutney #vegan #spicy
Dr. Dos's personal website. A collection of projects, webpages, writing, and other creative endeavors featured within.
I wrote a post mortem for my latest Ludum Dare ZZT game!
The Quick Hack vs. Developing Software
I find that I operate in one of twoĀ modesĀ when Iām writing software. Iām either approaching a project asa quick hackĀ or asĀ developing software. As much as anything else, this affects how I approach the project and what kinds of results that I get.
When Iām operating under the auspices of the quick hack, everything is moving toward and subordinate to the goal. The end product of the quick hack is everything. I approach the actual hacking in a fit of pique, itāsĀ annoyingĀ that this thing isnāt done yet. I always take the way thatās most expedient and Iām always looking for a shortcut or quick fix.
When I set out toĀ develop softwareĀ my mindset is different. Here Iām nurturing a seed of an idea. Iām taking small pieces and building connections between them. I have the sense that Iām making something new, or at least Iām making something thatāsĀ mineĀ ā I feel ownership. I also assume that the thing that Iām building has to last.
The natural habitat of a quick hack is a framework. When Iām confronted with something that doesnāt fit, I look for that next StackOverflow answer thatāll tell me how to shoehorn it in among the Tetris pieces that I already have. The framework is not malleable, I must square-off my round peg.
Libraries are what support developing software. Properly in charge, I choose a subordinate library and apply its talents appropriately. There is no hint of having to make my design fit within the strictures of someone elseās plan. I have the skeleton, I merely need the flesh. If I find that a library no longer suits my needs, it is easily removed. Well-scoped libraries tend to match one another much more closely than frameworks do. The problem that the library solves, the abstraction that it grants, tends to be more universal than a framework. Two HTTP client libraries will tend to expose those actions that HTTP supports. With a framework, I must first accept its world-view before I can start using it.
As Iāve grown as a software developer, Iāve come to believe that whenever possible I should use libraries over frameworks. This has been said many times before, but now IāmĀ getting thereĀ via my own experience. Iām beginning to see that the advantages of frameworks can be matched by a powerful language combined with a little sense about the high-level architecture that the application demands. Over time, Iāve developed my own palette of designs and code to accomplish most tasks. I can act as a linker, assembling only those functions that are needed to accomplish the task at hand.
Lastly, I worry that time and brainpower that I pour into frameworks goes unrewarded. When I donāt want to use a framework, the framework changes, or I want to do something that the framework doesnāt support, Iām left out in the cold. All of these scenarios play out often. Each time a new version of Rails comes out, it is infused with whatever OOP fashion is reigning at the time: concerns, presenters, etc. The way that IĀ usedĀ to do something is rendered obsolete without warning and without recourse. The knowledge that I had about how to work with the framework has gone stale ā like money, āyou canāt take it with you.ā
I think that it is time that we, as software developers, become responsible for our own fate. Make decisions, find out what works, learn! We have no excuse for being held hostage to decisions that we didnāt make just because we didnāt understand the nature of the decision. Software development is more than just filling in the blanks on some giant MadLibs of a framework. Software is the most infinitely pliable medium of design that the world has ever seen. Like a proof, if you can show your reasoning to be sound you can do it that way. Thereās no limit, so go out and build!