Posts

How to Make small Aquaponics wicking bed kit. (Architect's Exploded plan)

Image
1. Get your fish-tank. The recomended minimum size for a fishtank is 200 Liters as one block unit. Drill 2 holes on opposite sides and tie some nylon string as 'braces' to prevent the tank from buckling when it's full. the top 'oblong' shape will bend outwards when the tank is full, and this will cause cracks. So you need to keep the oblong shape of the tank, by tieing 1 or 2 "strainers" across the lesser width. Cost: $60 2. Build your table to sit above the fish tank Click Here for >>> Free Plans for stable table <<< The table should be stable so the legs wont cave in. The table should be light enough for you to carry into place during installation. if you can attach wheels to the whole thing, so you can move the kit. Great! 3. Get your wicking-bed tank The wicking bed should be at least 30cm deep, and a max of 40 to 50 cm deep. Having one wicking bed instead of two or more in sequential series, is better. ...

Role-model checklist . GitHub File Check with Rubrics - chatGPT.

Test your monolith or module's file and give it a score 1. Role-Model Source File Checklist (Yes / No) You can literally print this and go line by line. A. File Structure Does the file have a clear top-to-bottom order (for example: imports → constants → types → internal functions → exported functions)? Is everything in the file clearly part of a single module or concern? Is the file short enough that you can scroll through it without feeling lost (for example, roughly one screenful or a few screens, not hundreds of lines of unrelated stuff)? Are there no obvious “god functions” doing too many different jobs? B. Naming Do function names describe their purpose, not their implementation details? Do variable names reflect domain concepts instead of single letters (except for tiny scopes like loops)? Is naming consistent with the rest of the project (same terms for same concepts)? C. Interfaces and Behavior For each exported function or class, can you...

Chronological start in the Holy Bible.

There are three starts in the Holy Bible. One might read Genesis 1:1 and say that is the start. Moses wrote the book of Genesis as Moses was dictated by God. The story of Moses starts in Exodus chapter 1, as autobiographically written by Moses. John 1:1 is before even Genesis 1:1 .  John 1:1  Understanding John 1:1 is quite the intellectual task. It describes the eternal life of Jesus. On its surface, it posits that the Word was used by the Eternal God to describe God. Eternal implies God is first, and we can read that into the verse. "In the beginning was the Word, and the Word was with God, and the Word was God." That is, to imply that time begins, and the beginning of time starts with the Word, and since at the beginning before creation occurs, there is only God, so the word which started time, then can only describe God. Are we then positing that Jesus the Word, is as eternal as time, and less eternal than God? Then we are missing a peice of the puzzle, a peice revealed b...

Juggling with Google's Gemini's Canvases

All canvases are listed in the filing cabinet icon at the top right of the Gemini screen, on your browser's desktop mode.  Tip 1: The "Master Canvas" or "Table of Contents" Method (Your Core Problem)  This is the most effective workaround for managing multiple canvases in a single conversation.   Create a Master Canvas :  At the very beginning of your project or complex conversation, create a dedicated canvas for navigation. You can start with a prompt like: "Create a canvas for me that will act as a table of contents for this entire project on [Your Topic]. Title it 'Project Dashboard'."  Generate and Link:  As you work, whenever you need a new, dedicated space for a sub-topic, create a new canvas. "Okay, now create a new canvas to brainstorm marketing angles for this project." Get the Link: Once Gemini creates the new canvas, click on it. In the top-right corner of the Canvas interface, you'll see a "Share" button. Cli...