On the flip side, if/when I ever go for surgery I'm pretty damn glad we don't have the same requirements to perform surgery as we do to write software.
Whenever I fork a repo I rename origin to “fork” and then add the parent repo as a remote named “upstream” so i can pull from that, rebase any of my own changes in to, and push to fork as needed.
Multiple remotes is also how you can combine multiple repos into one monorepo by just fetching and pulling from each one, maybe into different subdirectories to avoid path collisions.
This sounds like submodules, but I'm guessing it's completely orthogonal ... multiple distinct remotes for the same _repository_, all of them checked out to different sub-paths; does that result in all the remotes winding up with all the commits for all the shared repositories when you push, or can you "subset" the changes as well?
Yeah, it's different, I was thinking about a time I needed to combine to separate repos into one. To do that, you clone one of them, then add a remote to the other one, fetch that, and `pull --rebase` or similar, and you'll replay all of the first's commits on top of the second's. I can't remember what I was thinking about the subdirectories, I guess they'd already have to be organized that way in the various repos to avoid conflicts or smushing separate sources together.
I’m finishing up a DIY ground install and just the conductor from the array to the service panel cost the same as about 3 panels. It’s about a 150 meter run.
Some very rough numbers from memory:
- 20 panel + 10 microinverter bundle: $5600
- cost to ship the bundle: $700
- conductor: $450
- steel/pvc conduit for conductor sheath: $350
- strut for racking: $500
- 3” steel conduit for ground mount: $5000
- concrete and tube forms for vertical post footers: $400
- augur/trencher rental: $500
- brackets/fasteners: $600
- tools: $500
- electrician work to upgrade service panel: $2500
- electrician work for hookup and disconnect install: still TBD but I’m guessing more thousands
- time spent x my current hourly salary as a programmer: I don’t want to think about it haha
Probably a bunch of stupid little stuff I’m forgetting. Just gas to go on supply runs is probably over $100, although I always tried to batch runs with other normal errands.
The most expensive parts of projects can be surprising, at least to me. I also recently invested in my own fuel transfer pump to transport home heating fuel instead of paying for delivery. 55 gallon drums: $20 each. Pump: $200. But the most expensive part was actually the 15 meters of arctic grade fuel hose at over $400.
For sure. I've recently done my back yard with weathering steel raised beds and larger wooden privacy blocking partitions. I'm doing all the cutting and welding myself, so needed a heavy duty 220v high amp extension cord. Built my own, but the insulated copper cable for that was a pretty penny. Cutting wheels, grinding disks, and welding supplies add up in cost quick. That and all the different fasteners you need. And pity the thought of using any decorative brass or copper....
> I'm doing all the cutting and welding myself, so needed a heavy duty 220v high amp extension cord. Built my own, but the insulated copper cable for that was a pretty penny.
300V 6/3 SO cord is about 6 bucks a foot, that adds up quick! Just be glad you didn’t have to buy any pin and sleeve connectors ;)
You can save the $700 freight shipping if you live near a distributor. https://www.sunhub.com/ and https://a1solarstore.com/ both have local pickup locations and extremely good deals on panels. Rent a pickup truck (or a trailer), show up and they'll drop a palletized bundle in your bed. It's also nice because you aren't hoping the freight shipping company handled them perfectly or dealing with damage claims. I picked my panels up in New Jersey from two different places, was easy.
Depending on your local area, if you're the homeowner, you can often do most of the electrical yourself (pull permits if needed). Use ChatGPT to look up code requirements and instructions, then look up YouTube videos where professionals show you how to do it all. I think it's much less complicated than figuring out all the solar-specific stuff (tilt angles, voltages, wiring, disconnects, etc).
Sadly couldn’t. I was able to get free shipping from a distributor in San Antonio to Tacoma, then transshipped it to Alaska with Carlile. And same story there though, forklift right into the truck bed!
Plenty of RVs have rooftop solar panels that'll routinely travel at 65 mph into a 35 mph headwind with no trouble. They're mounted with just plenty of little L-brackets screwed into essentially a plywood roof. Usually an RV roof has lightweight metal struts underneath for load support, but that's not what the solar panels mount to, that's mostly to carry the weight of a person standing on the roof. Never heard anyone have wind shear issues, the only trouble the L-brackets cause is water intrusion when the caulk ages and fails.
Solar panel weighs like 50 lbs. Think of it as a sheet of plywood. Not only do have to support the weight but have to worry about the wind load.
You can use wood, but then you have buy good amount of treated lumber and put it together. Galvanized steel also lasts longer than wood.
My impression is that galvanized steel fences are cheaper than wood ones. Even using steel posts and wood panels. People make wooden fences cause prefer the look.
Yep, snow load is a concern, but they’re mounted at a high angle due to our latitude. That does however increase wind load, and we’re located in somewhat of a gulley that funnels wind. I saw a friend’s professionally installed ground mount buckle under a failed piece of strut so figured I’d splurge for stronger stuff where possible, especially since I’m DIYing it and looking forward to the tax credit, reducing costs to match.
Plan mode is the extent of it for me. It’s essentially prompting to produce a prompt, which is then used to actually execute the inference to produce code changes. It’s really upped the quality of the output IME.
But I don’t have any habits around using subagents or lots of CLAUDE.md files etc. I do have some custom commands.
Cursor’s implementation of plan mode works better for me simply because it’s an editable markdown file. Claude code seems to really want to be the driver and you be the copilot. I really dislike that relationship and vastly prefer a workflow that lets me edit the LLM output rather than have it generate some plan and then piss away time and tokens fighting the model so it updates the plan how I want it. With cursor I just edit it myself and then edit its output super easy.
I’ve even resorted to using actual markdown files on disk for long sets of work, as a kind of long term memory meta-plan mode. I’ll even have claude generate them and keep them updated. But I get what you mean.
Right, “parent branch” implies a tree structure, but git is a DAG.
You might have a specific workflow such that you can actually answer your question, but it won’t generally apply to all repos.
Since a branch is really just a label for a specific commit, which may be at the end of a chain of successive parent commits, a branch isn’t really a first class structure, but a derived one.
You can get the fork point of a branch, which is a common ancestor commit shared by another branch, but that fork point is a commit and may not have a branch label. That commit can have any number of other branches going off of it: how would you decide which one is the parent vs just another sibling?
My assumption after looking at jj is that it is not as complicated as git yet. Give it time. It’s also not even as simple as git for many tasks, based on their own docs: https://jj-vcs.github.io/jj/latest/git-command-table/
If you're starting from the perspective of a native app developer, you're absolutely correct. However, most startups are going to be websites/Electron/CEF apps. It's much easier and cheaper to write-once-ship-everywhere with an ugly React UI than it is to jump through the hoops of writing special-snowflake versions for every OS under the sun.
It's basically negligent to insist on native apps, if profitability is your goal. I love native interfaces too, but the staunch belief in businesses being a "good native citizen" is a dead meme. It's cart-before-horse logic, we don't ever see anyone commit to the idea and reap real rewards. Native platforms punish you for playing by the rules.
It depends who your application is for. You obviously think building an application is about maximizing your profit, and your users are just a means to achieve that. If you were approaching your application from a “what’s best for my users” angle you might make different choices.
If you are running a business with limited funding (which is most businesses), then your primary need is to seek profit in a world where profit is often never achieved at all. Otherwise, your business ceases to exist, along with your app. Sometimes that does mean emphasis on strong design, which I’d argue means delivering a great experience to your users rather than a native or non-native design choice. Other times, you’re serving a demographic that doesn’t care so much about that, and your focus is on functionality above all.
