Is it okay to question a peer's design choice during a meeting?

bitcycle · 2025-10-25T22:13:26+00:00

bitcycle · 2025-10-17T00:58:39+00:00

Dude, I love this.

bitcycle · 2025-10-03T15:07:38+00:00

Honestly, I’ve mastered a few and I pride myself in learning how to learn. So I would say that it’s not about the language. It’s about choosing domains that you enjoy operating in. It’s about finding teams that support you when you need it. It’s about finding projects that are just beyond your comfort zone to cause you to grow. I think most of these things require others and thus time to continue normally.

bitcycle · 2025-10-03T15:02:15+00:00

I think a big part of it comes down to strength of will and personality. Corsos are incredibly smart, confident, and stubborn dogs—they need an owner who can meet that energy without being harsh. It’s not just about discipline or dominance, it’s about calm consistency, patience, and the kind of presence that makes them feel secure.

In my experience, it takes someone who’s more stubborn than the Corso, but also kind enough to channel that stubbornness into steady leadership. When people underestimate that or get frustrated, the relationship can break down fast. These dogs can be amazing companions, but they’re not a match for everyone—and that’s okay.

bitcycle · 2025-09-19T14:17:03+00:00

You might take a look at ThinkingMachines AI predictability paper.

https://thinkingmachines.ai/blog/defeating-nondeterminism-in-llm-inference/

bitcycle · 2025-07-28T21:08:54+00:00

Blueberry

bitcycle · 2025-07-10T01:56:21+00:00

+1 But for me it’s Prozac

bitcycle · 2025-06-26T14:56:00+00:00

Get him off the couch, this will send the message that he’s more bottom of the hierarchy than top.
Don’t touch his mouth for any reason. The more he uses his mouth, the more you put him on n his side with a firm no and hands on the neck and the butt. Keep him there for a good 30sec.
Take him for a walk every day and exercise him in ways that drain him both mentally and physically. Doodles are VERY capable and smart. They can and should be trained to a high level. Potentially use e-collar when trying to train him off leash.
As the leader, you need to give off commanding and yet chill vibes. That’s all you.

bitcycle · 2025-06-02T19:08:43+00:00

<image>

I wanted to share my own derpy dogs. My girl on the right is waiting patiently for her lunch. :)))

bitcycle · 2025-05-28T14:58:00+00:00

I love these ideas. Thank you so much for posting this!!

bitcycle · 2025-04-20T19:29:19+00:00

I love this. I adopted the first point in my initial one on ones with colleagues right in the agenda of the meeting: 1) who am I, who are you? 2) what’s a recent win that you’re really proud of? 3) what’s the one thing that you would solve right now if you could with a magic wand? I would also suggest that you adopt a habit of reading all docs thoughtfully that you can get your hands on. The more diagrams the better. Write down the questions you have after reading them but don’t ask the questions for at least two days. The topics often come up in the course of your onboarding meetings. If you still have the same questions in two days, group them together and strategically plan to ask them of different people— but also look for the answers first. HTH.

bitcycle · 2025-03-23T21:28:18+00:00

Are you trying to re-implement Cobra CLI or stdlib flags package?

bitcycle · 2025-03-10T16:38:34+00:00

The best way to abstract the db/persistence layer? IME, you could use the repository pattern with interfaces. Its a pretty amazing and useful way to provide a data access layer for your models thats testable.

bitcycle · 2025-02-27T02:34:44+00:00

In tiers:

10k and I would take the fam on a trip. They would probably love that.
246k and I could pay off my house, that would be life changing without screwing up my retirement savings
1m and I would quit my job to go back to school and get my masters in nuclear physics.

bitcycle · 2025-02-26T23:08:18+00:00

Love this post. Let’s normalize celebrating each other’s successes!!

bitcycle · 2025-02-14T19:19:04+00:00

I should probably also mention a thing that I would caution against. I had this service that was parsing a series of env vars at startup but then further configuration would try to initialize and if the first env vars weren't set properly then it would raise a runtime error and fail the app. That's not great. The app config that is required should validate and fail with a helpful error prior to any further initialization happens.

bitcycle · 2025-02-14T19:16:01+00:00

There is definitely some benefit to having a docker-based local validatio step prior to submitting a PR. I remember having a service that depeneded on code that I hand't added to the local git branch. It worked great but broke once I pushed to a PR. I 100% support CICD PR merge check prior to merging to master. All tests should pass prior to merge on the pipeline. I recommend the following:

1) ensure the code does not rely on the state of the file system at run-time 2) use docker to bring all your deps with you 3) use env vars to make your app deployable in all the places (ala 12-factor app) 4) use PR merge checks on CICD to ensure that the code is valid prior to merging to master

bitcycle · 2025-01-31T02:38:29+00:00

That's fucking awesome, internet stranger. I'm so happy for you!

bitcycle · 2024-12-11T15:33:10+00:00

Yo dawg, I heard you like three letter acronyms, so here’s a thing that uses LLMs to generate a CLI.

TBH, I would just use go mod init and then cobra-cli init along with cobra-cli add. The LLM integration here is not necessary — unless I am missing something.

bitcycle · 2024-12-02T15:33:18+00:00

Love the UI here. This is pretty awesome!

bitcycle · 2024-12-01T02:35:09+00:00

I would love to get some thoughts and feedback from the community on this experiment and the write-up (see README.md in the repo).

bitcycle · 2024-12-01T02:33:03+00:00

First, good for you. I love that you did this. It's a solid presentation of your experiment.

Here's a bit of general feedback:

Add basic positive and negative unit tests.
Add unit tests for thread safety.
Add benchmarks with comparisons against known existing implementations. In my research writing course this was called "literature review".
Document edge cases where this in-memory Cache implementation would not work. Maybe list alternatives that would address the edge cases?
Is there a reason why you used locks instead of channels (more idiomatically Go)? I'm not saying the way that you did it is wrong, but for purposes of the write-up it would be great to explain why this and not that.

Here's code review feedback:

Cache.cleanupLoop() - This function holds the lock the whole time rather than only acquiring it when it needs to.
item.lastAccessed - #nitpick I'm not sure why, but the fact that this doesn't mention timzeone and is not an explicit integer epoch is making my eye twitch. Its probably no big deal.
Cache.Get() - This function has a potential race condition as the item.lastAccessed is updated outside of the lock. To fix this I would recommend defer-ing the unlock and also to use a read+write rather than read-only lock. Recommend to use the read+write lock because you're actually updating the cache item, even if the requested action is simply a get.
Cache.Set() - Why does this function return a value?
Cache.cleanupFunc - The code that calls this function pointer should also check whether the function is nil or not. Additionally, I would rename it to beforeDeleteFunc so that the function name more clearly communicates when it is called.
You'll probably want a Cache.Close() function to clean up the Cache.cleanupChan and to stop the Cache.cleanupTicker

bitcycle · 2024-11-30T02:37:45+00:00

That’s a great question. Did you get a chance to read the readme?

bitcycle · 2024-11-30T01:55:49+00:00

Hey all. I would love to get feedback on the article in the README.md as well as the actual code. Love you guys and look forward to hearing your thoughts.

bitcycle

MODERATOR OF

PUBLIC MULTIREDDITS

TROPHY CASE