I am a frontend dev and use Firefox as much as I can. But I can't use it for development. Firefox's dev tools need to be better. I use Chrome for development because Chrome has great dev tools.
I've been trying to use GIMP for years (since Corel destroyed Pain Shop Pro). I don't do a lot of photo manipulation so I don't put in a lot of time learning. PSP had a UI that was discoverable for an amateur occasional user. GIMP has a UI that is completely inscrutable. +1 for Photopea, it has become my go-to.
If you are having problems with Windows RDP then the problem is somewhere else along the pipeline, not RDP itself. No other remote solution I've used is even in the same ballpark as RDP in terms of responsiveness and quality. RDP on a LAN is very usable for actual coding work.
Keep in mind that many (most? all?) LLMs are not trained strictly on factual data, and are probably not trained to differentiate between factual and non-factual information. If you ask an absurd question you will likely get a (delightfully) absurd answer. If you ask a question somewhere in the borders between reality and fiction... results may vary.
I interviewed for a software engineering position at USAA. After seeing the incompetence of the interviewers none of the nonsense they do surprises me.
> I’ve said this before, but Apple is forcing third party devs to be in service of Apple
I got my first taste of computers on early 90's Macs and was enchanted. Within a year I discovered DOS, Windows - and freedom. I did tech support for both Mac and Windows computers for several years. It's always been abundantly clear that the Empire of Mac exists for its own glorification (and obscene profits) - customers, developers, partners - they are all in service of Apple. It's unfortunate that Apple does some things with unparalleled quality and maintains a loyal following, because the apple has always been rotten at its core.
I loved Chrome's debugger for years, then build tools and React ruined debugging for me.
Built code largely works with source maps, but it fails often enough, and in bizarre ways, that my workflow has simply gone back to console logs.
React's frequent re-renders have also made breakpoints very unpleasant - I'd rather just look at the results of console logs.
Are there ways I can learn to continue enjoying the debugger with TS+React? It is still occasionally useful and I'm glad its there, but I have reverted to defaulting to console logs.
My thoughts exactly. JSX provides the best templating syntax I have seen - it's just JS, and it uses curly braces to delineate JS. Putting JS, or worse, custom syntax in strings is terrible, and every other delineator choice is less idiomatic and uglier than curly braces.
I really feel like this article should also mention the rate of formation of new stars. According to [1] Universe Magazine the James Webb telescope has revealed that more than 3,000 stars are formed every second.
GIMP is astonishingly bad. I got by for many years with Paint Shop Pro, even through its steady decline after Corel acquired it, but eventually they destroyed it. In desperation I turned to GIMP but it is so bad that I now use Photopea. I would pay for a modern functional equivalent of Paint Shop Pro, but I don't know that it exists.
I spent a week learning Laravel and modern PHP for a project that never materialized. I am so grateful the project never materialized, because for all the past 2 decades of improvement PHP remains a language I never want to work with. There may be some details in "A Fractal of Bad Design" that no longer apply, but the phrase itself still very much applies - PHP (and Laravel) remain a fractal of bad design.
Sounds like you have had the misfortune of using terrible banks. I have never had this issue with home mortgages or car loans, it was always easy to make extra payments directly to the principal.
Staging can be a helpful alternative to micro commits. I'll write some code, make some progress, revise, and once I get a small changeset that I'm happy with I stage it. Then I'm free to make a bunch of exploratory changes and the diff will show only those changes, and I can back them out easily. I move forward bit by bit like this until the feature is done then commit.
I have a bit of a preference for this approach as well, but having worked on numerous large projects I have to agree with Josh's arguments against it. Maybe on a small personal project it can succeed but on large ongoing projects I favor organizing by function rather than feature.