bryanculver

I started down this path, although with a VS Code plugin, but I didn’t find the ability to visually tie into the text editor with chat modals/bubbles. It’s likely what I would pivot to if I don’t like the amount of effort necessary to build the basics.

I'm slowly building an IDE with mentor/skill-level awareness baked in.

I've noticed that juniors and new hires often fall into an impostor-syndrome trap when reading an unfamiliar codebase or reviewing a senior peer's PR. Documentation helps, but it usually runs into the curse of knowledge: it's written by someone who's spent so much time in the code that they've lost sight of what it's like to be new to it.

I've always liked the rubber-ducking process, and mob programming too, so I'm trying to combine both into a modern AI-enhanced form:

- "Duckies" with distinct personalities (really, skills) that each specialize in a particular kind of problem

- "Teachable moments" (working title): small bubbles that surface something novel, tangential, or foundational as you work

- Skill-level detection and a routing model, so the app doesn't overwhelm or annoy you with explanations you don't need

Each duck also runs on a tiered memory model, rather than one flat context window. There's a core memory, essentially the duck's resume, defining what it's actually skilled at. Above that sits a longer-term memory for company standards and code style, and a separate long-term memory scoped to the project itself. Short-term memory then covers whatever task or feature is currently in flight. The idea is that a duck should reason more like a team member with a real employment history than a chatbot that forgets everything between sessions.

It's called Duckies AI (https://www.duckiesai.com). It’s very rough, working locally, but not in a state I’m ready to ship yet. I'm hoping to ship an alpha soon. Turns out there are a LOT of table-stakes features an IDE needs.

A follow-up/related message would be great:

"To the Guy I Invited to My Wedding, Even Though We Have Never Met"

This will sound like cheating but I argue for the time it saves me, both in creation and on-going maintenance, and delivering a quality finished project: Squarespace.

The clients are happy, if they get to the point where they want to manage the content themselves, and for less than $300/yr they get hosting, access to a payment processor if they need it, and domain renewal. It's been a no-brainer.

"'I understood that reference' - Captain America" - Michael Scott

Will they make a couple more $ out of this? Maybe.

I suspect they'd rather not have a proliferation of developers farming out their profiles and dealing with it on the service/support side. Developers with pseudo-ownership of strangers devices and users who don't fully understand what they are agreeing to with tying their device to a unknown developer can't be fun.

I see that now. I wouldn't disagree, but if you're a CTO for example you might have interest in the services more than joining the team.

The article is fascinating but one thing I am finding very common on these engineering blogs is no easy path back to the company or service. Understandably the logo at the top goes back to the blog homepage and the copyright at the bottom is just static text.

I could search or visit one of the social pages linked to in the footer but it seem like an obvious link one would want to have.

So although there might be “waste”, emergency preparedness shouldn’t be forgotten about. It’s safer and better to have blood available when it’s needed than to be begging for it.

What I think they're saying is that with Adblockers, they can phone home which ads they block, URLs they see, etc.

Content blockers impose rules at the outset and the rule generator won't see what the URLs/content actually is.

The way I would think of it would be like "let me see what you're seeing and I'll let you know what to let through" vs "here are a list of things you shouldn't let through but I don't need to know about what the hit rate actually is".

Although I could be misunderstanding the implementation.

  - Random scratch files in ~/Desktop/Rug (purged monthly, no backup)
  - All development in ~/Workspace (routinely backed up)
    - Source controlled development in ~/Workspace/Repos/[entity]/[project name] (excluded from backups)
    - All non-SCed files in ~/Workspace/[entity]/[project name]
  - Downloads in ~/Downloads (purged daily of older than two weeks, not backed up)
  - Personal computer has ~/Workspace symlinked from a Dropbox folder: ~/Dropbox/Bryan/Workspace
  - Family photos in ~/Dropbox/Family/Photos/[year]/[month]/[YYYY-MM-DD HH-MM-SS].[format]
    (routinely push-only sync to Amazon Glacier)

  * Several cron jobs to help maintain everything
  * Several custom Zsh plugins to make jumping around in shell a breeze
  * Daily bullet journal+markdown style notes auto source controlled in
    ~/Workspace/Repos/Personal/eod/[year]/[month]/[day].md

Click and drag it to the right.

I started a company, Argonomo (https://argonomo.com) and we founded and soft launched two ventures:

- SafeWhistle: An anonymous, encrypted, privacy-focused whistleblowing and incident management application companies and institutions can implement to help cut down on lack of reporting and increase transparency. (https://safewhistle.com)

- Sidepitch: A venture management system targeting private equity groups and venture capitalists. Streamlining the application process for startups and giving investors a central management solution for their investments, instead of a collection of emails, paper documents, and in-face communications. (https://sidepitch.com)

If it's from @aantonop on The Kevin Rose Show (which I just got done listening to myself) he did mention that until the volatility comes down, prices can't be pegged to the Bitcoin (or many cryptocurrencies for that matter).

Example: At the moment of me writing this, let's say I wanted to be paid $50/hour for to develop a website. That is my desired value for my work. It's value today will large in part be the same next week, month, maybe even year. That would be 0.006086BTC. If I were to list that as my asking price instead of the less volatile $50, next week I could very quickly price myself out of the competition, surely goes the same next year (either direction). I continuously re-evaluate the the BTC asking rate based on the exchanged value to me. One day though, that won't be the case. Once the market stabilizes and dips and gains are less than 5% over the year, I can expect this to be unchanging and start valuing directly in BTC.

He mentions it in the podcast that several countries with highly volatile national currencies actually use a more stable currency (such as USD) to list an asking price for a good, but are actually paid in the their currency's exchanged value to that amount. (I'm still looking for a reference to such occurrence).

Although the value of what he was paid in yesterday has gone up (Got $5 worth of bitcoin yesterday, now worth $6) the cost of the product he buys tomorrow will inevitably go down (0.00075 today, 0.00060 tomorrow).

While I don't completely disagree with you in the large discrepancy between the two, I believe it's a gross over-simplification to state Priceline owns nothing. In the same over-simplification you could state that newspapers are worthless as a middleman to the actual events that happen. However what you are actually accessing is talent, resources, and services to compile that list of recent events every day (or in the case of Priceline: hotels, airlines, rental cars.)

Wow, in the last 100M seconds I've gotten married, bought a house, had two kids, graduated college, started my own company. That's one heck of a metric.

I had LASEK (a less invasive, longer recovery option to LASIK) a few years ago.

My suggestion is if you are at all interested in the procedure, and I would HIGHLY recommend it, is to find a doctor that performs both styles of procedures, will educate you fully on the pros and cons of both, and will offer recommendations with quantitative reasoning. I went with the LASEK route for many reasons, however my cornea in one eye was too thin to support the correction needed for LASIK with the number of microns lost due to the scalpel incision.

The largest issues are that the outcomes of LASIK/LASEK are quasi-permanent and that there are many more variables involved than just an eye exam, including your own calmness during the procedure.

My doctor offered, as long as the eye can support the number of microns lost due to the correction, to perform a followup surgery if results ended up being poorer than 20/30 after the first surgery, free of charge. It took a few days before I could see the results (an issue with the method of procedure) however I resulted with 20/20 in one eye and 20/15 in the other.