71–80 of 1001 posts
I changed gears and moved into the video games industry at the end of 2021. I started developing a city builder called Metropolis 1998 [1], but wanted to take the genre in new directions, building on top of what modern games have to offer: - Watch what's happening inside buildings and design your own (optional) - Change demand to a per-business level - Bring the pixel art 3D render aesthetic back from the dead (e.g R…
It is a pretty fun project
- Portable Secret (https://alcazarsec.github.io/portable-secret/) - self-contained HTML files that decrypt in the browser.
- Dead Man's Switch (https://alcazarsec.com/deadmanswitch) - sends messages when you stop checking in.
- Flare (https://alcazarsec.com/) - silent alert when your device is accessed without authorization.
I live in an old house. The front bump out leaks when we get driving rain. I installed some flashing but that wasn't enough, it's still leaking. So I'm working on that so I can close up the big hole in the ceiling some day. The prior owners filled in the old coal chute with literal bags of cement sort of artistically placed in the hole in the brick foundation. So I'm trying to figure out what masonry tools and skills…
Phase 1: Download the student's code from their submitted github repo URL and run a series of extractions defined as skills. Did they include a README.md? What few-shot examples they provided in their prompt? Save all of it to a JSON blob.
Phase 2: Generate a series of probe queries for their agent based on it's system prompt and run the agent locally testing it with the probes. Save the queries and results to the JSON blob.
Phase 3: For anything subjective, surface the extraction/results to the grader (TA), ask them to grade them 1-5.
The final rubric is 50% objective and 50% subjective but it's all driven by the agent.
Aside from that, I need to document and properly release one of the pieces that PAPER is relying on (some generic tree-processing code that makes operations on directory trees a lot nicer than with the standard library "walk"s), and work on others (in particular, a "bytecode archive" format for Python that speeds up imports for some projects, mainly by avoiding filesystem work at import time — I want to offer it as an install-time option in PAPER, and later have `bbbb` make wheels with the bytecode precompiled that way).
It makes connecting user domains to your app easy and reliable at any scale. Each Approximated user gets the own globally distributed, managed cluster of servers with its own dedicated IPv4 address. Includes (unlimited) edge rule features, DDoS protection, webhooks, and more. Make a simple API call, tell the user to point an A record at the IP, and it’s connected to your app with its own SSL certificates.
Built/building with elixir and phoenix, which has been fantastic.
I have some barebones content at https://struggle-meals.wonger.dev/ and will be working on the design over the next few weeks. Some decisions I'm thinking about:
- balancing between personal convenience and brevity vs being potentially useful for other people. E.g. should I tag everything that's vegan/vegetarian/GF/dairyfree/halal/etc? Should I take pictures of everything? (I'd rather not)
- how simple can I make a recipe without ruining it? E.g. can I omit every measurement? should I separate nice-to-have ingredients from critical ingredients? how do I make that look uncomplicated? (Sometimes the worst thing is having too many options)
- if/how to price things? Depends on region, season, discounts, etc