55 karma · joined September 28, 2014
Interests: Web Development, Technology, Startups
---
I prefer nx for single applications and move shared code to "libraries" (I use non-buildable libs). It's pretty sweet for larger projects.
If I truly want to search I will ignore the llm results, but I like the convenience of a quick llm search that knows "all the things". I get the answer to my question without searching multiple ad-ridden websites (since the ad provider does all the things)
But I may not have paid enough to get the full real experience with codex
My M1 air (I think 8GB?) had similar issues My M2 24gb was amazing - especially since it allowed dual monitors. I recently upgraded to the M4 32GB and it is my "do everything" computer and is absolutely awesome.
My personal experience with the m-series is that get as memory as possible. I do feel the M1 had issues based on the couple I owned.
EDIT: Even on 32GB my memory pressure is constantly in the yellow, but have not seen it go to red
Design usage shouldn't impact code usage.
Since the attacker had full control of the NPM account, it is game over - the attacker can login to NPM and could, if they wanted, configure Trusted Publishing on any repo they control.
Axios IS using trusted publishing, but that didn't do anything to prevent the attack since the entire NPM account was taken over and config can be modified to allow publishing using a token.
I use cmd+tab and cmd+~ a ton also as I have multiple browser profiles and windows open and usually a few instances of ide with different projects.
And always close tabs with cmd+w and apps with cmd+q to avoid running apps with no visible windows.
I feel super productive with this workflow, never need to fiddle with manual resize.
When someone is screen sharing and they have a bunch of random sized windows it drives me crazy.
I would (incorrectly) assume that a product like this would be heavily tested via AI - why not? AI should be writing all the code, so why would the humans not invest in and require extreme levels of testing since AI is really good at that?
But other than not understanding the data, the UI looks really fancy.
I just found out today that hovering over the green traffic light icon shows an arrange menu... but the "maximize" option there leaves some padding on all sides of the window - weird.
I swear by https://rectangleapp.com/ - same outcome but with keyboard shortcuts instead of the mouse.
cmd+option+f = maximize to fill entire screen
cmd+option+ctrl+left/right = move window to other monitor on left/right
I occasionally use cmd+option+left/right if I need to have two windows side-by-side on the same monitor.
MacOS window sizes have always felt weird to me - no easy way to maximize without making it go into full screen mode.
As I was writing this, I just realized that hovering on the green traffic light shows a menu to choose some window placement options.... not sure how I never realized this before, but even the "maximize" option there doesn't go all the way to the edges - weird.
The codex agent ran for a long time and created and executed a bunch of python scripts (according to the output thinking text) to compare the translations and found a number of possible issues. I am not sure where the scripts were stored or executed, our project doesn't use python.
Then I fed the output of the issues codex found to claude for a second "opinion". Claude said that the feedback was obviously from someone that knew the native language very well and agreed with all the feedback.
I was really surprised at how long Codex was thinking and analyzing - probably 10 minutes. (This was ~1+mo ago, I don't recall exactly what model)
Claude is pretty decent IMO - amp code is better, but seems to burn through money pretty quick.
https://skiwhitefish.com/ski-among-the-snow-ghosts-at-whitef...
It's one of those things that you don't realize how poor the performance is until you experience something better.
Mentioned from his blog: https://mitchellh.com/writing/ghostty-is-coming
I have a large application and I use next.js for the landing pages (landing, tos, privacy, blog, login, etc..) - but for the core application after login, I just use vanilla react with react router. For me I keep these as separate applications as I don't want to load the entire app just for the landing page or login box.
Every time I need to work in the nextjs part of the app I always run into problems and have to read the docs and troubleshoot, sift through which part of the docs apply to my setup versus the app router.
If your entire application needs to be indexed as a static site (e.g. content based versus a web application), then vanilla react isn't a good fit - so it depends on your needs.
Unrelated - but shout out to https://nx.dev. I always prefer using this for all of my projects - made it super easy to have my node backend, react frontend, nextjs landing page, chrome extension, cron jobs, etc.. all in the same codebase where I can share code between all of them via non-publishable libraries.
I normally just record the jam and get a link and paste it wherever, but I love the ability to have Jam create jira tickets for me. And THANK YOU for making it easy to choose the sprint! the Slack Atlassian plugin makes it impossible to find the sprint and shows all the closed sprints that cannot be used for new tickets.
Really an awesome tool. I have been using it to report bugs for any random open source project I am working on.
Likely an output of so many electron based apps which are memory hungry, but if the memory is supposedly "really fast" then I would expect better performance. Never had the issue with Intel.
But with a nice bit or memory, the performance is really nice.