buit a keyboard driven calendar webapp right now cause im disappointed with all tho other solutions i could find. no dependencies, super customizable, im kind of obsessed. for the first time in my life im actually keeping my calendar alive.
Anthropic uses token billing for Claude Tag. But itโs different from CC - itโs an AI Colleague, so Iโm asking PM and EM to talk to it instead of to me - accountability switches.
No, Claude Tagโs PRs are my teamโs. Slop PRs come from outside of the team.
Anyways, dozens PRs per day is draining energy. Donโt want to review anything anymore.
I wonder if it's okay to keep posting in Japanese here.
I get the feeling the site creator wants this to be a place where speakers of various languages can talk together.
/post/1045
I looked at your personal website. I too am my own worst enemy and afraid to write.
I feel like I have something to say but at the same time I don't know what to say. How can that be?
@fastidious๐profilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerswrote:
The interface needs some work. For example, I would like the textarea that I am using right now to be as wide as the header above. Also, where is the character counter?
A lot of people write so much software to sandbox their AI agents.
I say don't bother. Just give your agent its own non-admin local user account. It's easier and much more effective.
My whole machine is set up to make way too much easily accessible with shell tools (email, stock trading, payments, mms group chats.) I can't trust it.
I canโt trust it enough to give local access as well! Having a hard time to let go of control.
@carbonwriter๐งprofilefollow(\ (\
( โข โข)
โโชโชโโโโ
Full of mostly true stories, I occasionally write them down. Habit of talking to anyone. Bipolar. Author.wrote:
Huge flaw in the static site generator I built.
That's what you get I guess when you don't have a computer science degree and you build with only surface level knowledge. You get your ass bit!
I assume this is not original at all at this point - but (extreme) DRY is not a good practice. My experience is that a bit of copying yourself and your colleagues in the code base often make maintenance of the code base easier.
@honey_ohs๐ฅทprofilefollowSoftware engineer. [Reluctant] Salesforce dev. Salesforceโs biggest hater.
stephenlf.devstephenlf.devImportant Thingsreplied to@asmund๐ฅทprofilefollowFather, getting older every day, technologist, enterprise architect @ work, like to explore tech. Like to keep it simple and work in the shell, write in vim, prefer Debian if I have the choice. Plays saxophone and clarinet. Enjoy motorcycle riding, photography, hiking. Christian.:
Many have adopted the term WET (write everything twice)
Uncompromising adherence to DRY.
First copy-paste? Fine by me. Second? I'll still let it slide. Third? OK, now let's think about finding a suitable refactor.
Getters and setters for everything. Certainly, if you want an object to be doing more than just getting and setting a value right now, get them in there!
Planning to add functionality later without breaking code? Stop it! That should break code! If I'm consuming a library and have been using this setter method for 2 years, I don't want it to suddenly introduce brand new validation, caching, or logging behavior!
Are getters and setters on everything even considered a good practice? To me it screams junior developer who hasnโt yet fully understood encapsulation and abstraction โ if youโre just exposing getters and setters as the interface then what is the class/module/etc providing beyond what a standard variable doesโฆ?