HN user
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.
Yeah I'm not finding it compelling to listen to someone's ideas about "taste" when they think that font is tasty.
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.
npx http-server (keep the "r" at the end, it's more up-to-date than the http-serve package)
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.
[1] https://universemagazine.com/en/james-webb-comes-closer-to-r...
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.
Remote development is VSCode's killer feature.
This is what you get when "frontend devs aren't real devs" and every job wants a "full-stack dev" (surprise, they can't do frontend!).
I have seen several Waymo cars stopped for no good reason or blocking the street while very slowly trying to figure out what to do.
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.
I went to the article hoping for more context, but it just leaves that statement about more than half of the crew dying without any explanation.
I failed a technical interview at a large financial institution and I'm sure the interviewers thought I was stupid. As I gazed at the atrocious code they wanted me to make changes to and listened to them misuse programming terms as they tried in vain to communicate what changes they wanted me to make I'm sure my bewilderment was all over my face. Everything else about the company was great, but all my enthusiasm died when I saw into the engineering side of the business.
Razer is a terrible company, which is tragic because they started out as an amazing hardware company. When they pivoted to being a spyware company I stopped buying their hardware. I've been happy with SteelSeries so far. Their Rival 500 is a great mouse if you want lots of buttons and configurability.
As a front-end dev who works with JS all the time and never writes shell scripts, every time I have to deal with shell scripts I think "I'd really rather use JS for this".
Process Explorer (from sysinternals) lists processes as a tree so it's easy to find and kill the root Chrome process. At a glance it looks like all non-root processes have a "--type" parameter given to them. The root process has the simplest command line with only "--remote-debugging-port" being passed.
What are the cases where Dropbox works well for people? Years ago I used to regularly have people tell me "my computer is slow, how do I fix it?" I look at their running programs, uninstall Dropbox, and their computer is no longer slow. I hoped maybe a combination of better resource usage by Dropbox and increasing computing power had alleviated that issue, but just the other day another person called me with slowdown issues and sure enough the culprit was Dropbox, which they had just installed.
What is the obsession with laptops? While I fully understand they have their uses, I don't understand why someone who is employed full-time doing programming would cripple their own work environment by using a laptop. I've been hearing and reading about laptop complaints for years from "professional" programmers. It's very easy to avoid so many problems by building your own desktop. If money isn't an issue then just buy one prebuilt.
Subnautica is a wet-your-pants game of sheer terror. However, if you disable damage and aggression you can focus on beautiful and peaceful exploration and building and gardening. A very iyashikei experience for me.
Razer went from making great hardware and drivers to making terrible drivers that require you to sign in to a Razer account and constantly run Razer software. I was a Razer die-hard for years, but with their transition from a hardware company to a cloud-based user-data-mining company I avoid them. If you want good hardware with good drivers I highly recommend SteelSeries.
It will be nice if Firefox restores support for high-quality scaling. transform(scale) used to work well, then for a long time it produced horribly pixelated text. They improved it a few months back, but it's still noticeably pixelated. Chrome is perfectly smooth.
Sadly, our green wave is synchronized with a 50 mph speed, but the posted (and reasonable) limit is 35 mph.