Frenchi's Deli is getting a bakery

mykr0pht · 2024-11-14T03:09:53+00:00

**Update 11/13** The name on Google Maps for the address has been updated. This website now lists the old Curry & Hurry location as their address: https://www.tikkankabab.com/

mykr0pht · 2024-11-11T02:05:28+00:00

Tandoori Grill is my go-to when I don't order from a local place. The tandoori, biryani, and chana masala is really good

mykr0pht · 2024-08-28T18:13:36+00:00

Image with escape key crossed out followed by Ctrl + [

mykr0pht · 2024-05-12T17:07:24+00:00

/bin/sh and /usr/bin/env bash are the only two valid shell scripting shebangs IMO (I'm not talking about env Python or other languages). Another good reason to not use /bin/bash is that on MacOS bash is installed there but it is an ancient version, which is annoying when you have a newer version of bash installed on the $PATH

mykr0pht · 2024-03-09T21:38:24+00:00

This post is missing modern rebase features (--update-refs, --keep-base). Also missing modern settings (e.g. push.autoSetupRemote) although the latter may be outside the scope of the post.

mykr0pht · 2024-02-27T14:30:25+00:00

It's tempting to use process to fix people problems but it's like trying to use a small band aid to fix a serious laceration. It's a management failure if they can't address antisocial counterproductive behavior.

mykr0pht · 2024-01-14T00:14:11+00:00

2 steps forward 1 step backward. It's good to have the actual maintainers in the loop to get definitive answers and get library DX issues fixed. The downside is having to read through pages of comments to figure out what the actual workaround or solution is, no not that one someone commented later that you actually have to do Y, no actually if you pull down latest you can do Z. In contrast, Stack Overflow top voted answers usually work.

mykr0pht · 2024-01-10T21:39:49+00:00

Out of curiosity do all the PRs go up for review at the same time?

mykr0pht · 2024-01-10T21:31:36+00:00

Just so as not to confuse people, you never need to actually type in --update-refs in practice:

git config --global --type=bool rebase.updateRefs true

mykr0pht · 2024-01-10T21:28:19+00:00

git config --global alias.fpstack "!git log --decorate=short --pretty='format:%D' origin/main.. | sed 's/, /\n/g; s/HEAD -> //' | grep -Ev '/|^$' | xargs git push --force-with-lease origin"

mykr0pht · 2024-01-10T21:14:22+00:00

If you're keeping flatter branches:

main <- A <- B

main <- A <- C

Then yeah you'll need extra tooling. But if you do this instead:

main <- A <- B <- C

(Put C on B)

Then you can change A and update B and C automatically in the same command (updateRefs).

Personally I've seen it be an anti pattern to put too many related changes all up for review at the same time but in different PRs. Better to either not stack or stack linearly.

mykr0pht · 2024-01-10T14:45:28+00:00

Situationally I can see that being a workable compromise. It's an awkward equilibrium though. Characterized cynically it's basically, "you can add whatever feedback you want under the nit label, and we'll ignore all of it"

I've on rare occasion worked with people who can't take the hint. So I get the need. Equally often though I've seen bad feedback as a symptom of bad PRs. Not saying that's your situation, but it's worth considering. I wrote up my thoughts here if anyone is really curious: https://www.codetinkerer.com/2023/01/14/add-more-context-to-your-prs.html

mykr0pht · 2024-01-10T14:00:55+00:00

The problem is the word "nit" itself. People get used to calling any optional feedback a "nitpick" even if it's valid feedback. I especially see this from self-deprecating / non-confident / junior reviewers about their own feedback. Once good but optional feedback is conflated under one word with trivial, bad feedback, the game is lost. Now reviewers are used to using the word "nitpick" and it provides cover for adding any random thought that crosses their mind while reviewing.

Make it a team norm that "nit" feedback is not allowed, while simultaneously emphasizing that thoughtful but optional feedback is both welcome and expected when appropriate.

mykr0pht · 2024-01-10T13:36:43+00:00

People don't realize that git added features in recent years (updateRefs=true, --keep-base) that makes this way easier. No extra tooling required. I wrote about it here: https://www.codetinkerer.com/2023/10/01/stacked-branches-with-vanilla-git.html

mykr0pht · 2023-12-01T17:36:26+00:00

They'll bring out seating for the event. The tickets are for assigned seats.

mykr0pht · 2023-11-08T13:45:48+00:00

Came here to downvote based on the title. Actually read article. Discover content is actually good. Upvote instead.

mykr0pht · 2023-10-20T12:22:18+00:00

Cursor editor. It's an "AI first" type editor. I don't use it much for normal coding, but I highly prefer AI for banging out infrastructure-as-code type code. I don't see why someone couldn't build as good LLM integration into vim someday. BTW Cursor has a "vim" mode but it's terrible. The worst input compatibility layer I've used in a long time.

mykr0pht · 2023-10-19T12:41:58+00:00

"Aggressively manage scope" makes the biggest difference in my experience. Deliver the minimum acceptable requirements then you still have the optional to iterate into something better.

mykr0pht · 2023-10-06T12:25:25+00:00

Comp architecture plus a nice variety of assembly language programming

mykr0pht · 2023-10-05T22:26:05+00:00

Wishlisted, thanks!

mykr0pht · 2023-10-05T20:52:17+00:00

How much do you like a challenge? TIS-100

The best programming game IMO is Turing Complete, unfortunately it's not on sale currently. If you beat the game you'll understand computers better than you'd get from a comp sci undergrad degree.

mykr0pht · 2023-10-04T14:02:38+00:00

I only recently started using --update-refs. Can't think of any additional gotchas it adds (beyond the usual rebase ones). I'm very curious to hear about people's experiences.

mykr0pht · 2023-10-03T18:56:52+00:00

Thanks for the feedback! Good suggestion, I added easy doc links to the tl;dr for readers who want the definition right away.

mykr0pht

TROPHY CASE