1,042 karma · joined March 26, 2016
If kids could have just instantly downloaded any program they wanted, they wouldn't have been copying programs out of the back of magazines.
Personally, I came a little later, but I also learned stuff because I had to in order to do the things I wanted to do. After enough exposure I realized it was fun and interesting.
> And yes, there's more to CS than programming, but not in a way that pays the bills
I'm curious what bill paying career you think is readily obtainable with a physics degree.
Moreover, while the GPT/LLM stuff is very exciting, it is coming out of the CS field. If you truly think it's transformative, that shows you the potential of CS and programming and is all the reason to pursue a CS degree.
Stick with CS if you like it—the career prospects aren't going anywhere. However, if you're just trying to get paid, there's always finance.
Well, to a certain extent all the AKC dogs have health problems. Even big dogs have stuff like hip dysplasia. Some breeds are healthier than others, but the most important bit is buying from an ethical breeder if you must get a pure bred. Sketchy breeding practices are what exacerbate the health issues in popular breeds.
I'm glad it's not just me! I was implementing Either<T, U> the other day, and found writing Left<T, U> and Right<T, U> a little dirty. Progress is progress though.
For web stuff, I'd suggest learning JavaScript if you're interested front end or something like Golang if you like back end. Those will expose you to the necessary concepts you need to perform in those roles without bogging you down too much in cruft. You can safely apply to roles for most languages if you can demonstrate your knowledge sufficiently.
Highlighting housing costs as a significant contributing factor is an important point to make, but there's no need to undermine the other contributing factors through bad faith arguments and cherry picked statistics. Yes, homelessness clusters in cities with robust social programs, esp. those with temperate weather. These same cities are also the most expensive in the US, effectively creating homelessness traps.
As for following in the footsteps of Houston, it's not nearly as feasible for these places. They have up to 10x the homeless populations and 2-3x the housing costs. Compare providing 5,000 units in Houston vs providing 70,000 in Los Angeles.
We should absolutely look to provide more subsidized housing to the needy, but it's clear we aren't aren't able to do it in the most in demand real estate markets in country.
EDIT: numbers
Metals is great if a bit buggy. Being able to just install a VSCode plugin and start hacking is huge. If you want to win new programmer mind share, improving Metals (or some other VSCode language server) is the way. Scalafmt is nice to see coming from Java.
The build tooling situation is awkward. Mill looks much more modern than sbt but clearly isn't the de facto choice. The general community displease about sbt further adds to the unease. The main take away here should be the onboarding experience to the build ecosystem does not instill confidence.
The difference between ZIO/Typelevel stuff is not immediately clear. Why are there two functional programming ecosystems? I guess it's a convention vs configuration debate? It seems like the two ecosystems should overlap then, but fair enough.
A single language level package repo would be cool for discoverability purposes, but I'm also used to the multi-repository thing. A directory or something to make packages more discoverable might be a good half-step.
Ammonite is fantastic, but along with Metals and all the other tooling I've used, it works better under Scala 2. Scala 3 is still kind of weird.
The biggest things to me would improve Metals, improve onboarding for build system, improve Scala 3 support for tooling all around, improve discoverability of defacto best/most active packages.
Tailwind accepts greatly reduced DRY for straightforwardness. It's kind of like inline styles with training wheels.
I'd much rather do this type of thing in the CSS layer, but doing it inline has advantages. Mainly, I think the reason it's caught on is new junior devs get productive in it very quickly.
From my personal experiences, I suspect the restriction of financial aid based on arbitrary cutoffs affects more people. I know several people who got into ivys, but didn't go because they didn't qualify for financial aid and chose not to take on large amounts of debt, coming from frugal lower/middle class families.
For formatting, the only compelling truly framework agnostic option I know is the google formatter (unconfigurable). The other options are either editor specific (IntelliJ and Eclipse configurations are incompatible go figure), cost money or are half-baked (prettier). Now I believe there's a way to use spotless (tied to gradle/maven) to use one of the IDE specific formatters across IDEs at the build tool level, as you point out, but that's kind of a different thing, heavy weight and working around the underlying problem. Compare this to gofmt, rustfmt, scalafmt, black, prettier/eslint, etc. that are fast, framework agnostic and require no boilerplate. Formatting is a solvable problem in Javaland to a degree, but wow is it unnecessarily complicated and fraught with decision points that can end up in bikeshedding committees.
As for boiler plate, I'm talking about language level stuff, like having to make a class and separate file for every simple data structure, then having to implement hashcode/equals for all those classes, etc. Where in other languages, you can just return a tuple or a result or what have you and get on with your life. Again, IntelliJ will just do most of this for you, but supervising my IDE in boilerplate creation is not a joyful experience. And if you skip supervision, you are basically saying the IDE is now a dependency and the correctness of your program depends on the correctness of your IDE. Not super great.
Anyway, IntelliJ is certainly an amazing piece of software that makes Java development more productive, but learning it, configuring it, etc is a whole thing. Other modern languages provide much better QoL features out of the box and have a much less incidental complexity that don't require an IDE to get around. That said Java has the best library ecosystem, the biggest pool of developers and solid performance.
You just gotta pick something and go. I know nothing about your app, but there's plenty of general purpose languages out there that wouldn't be a bad choice. Over-optimizing is gonna kill the fun and you'll get nowhere. Choose some tech that solves your immediate problems and maybe keep things modular so you can break out the pieces that aren't working later.
Remember the fun part is building things. So go build something.
Honestly just walking more is huge. An extra 2-3 miles a day of walking is pretty easy to work in—it takes like an hour. You can kill a podcast and get some errands done at the same time if you do it right.
In general, I don't love Rust's choice of sigils (::, <>, etc), but the language reads well enough. That inner/outer function thing is legit the compiler model leaking into user code though.
Lots of possibilities here!
I actually think those are fair reasons to switch to something more straightforward for a solo dev, but none of these are true showstoppers and the story for each will get better in time. Good feedback on the Rust in general.
I remember that one! The aughts were a truly a golden era in Japanese phone design. The technology was also waaay ahead of the west. We're just now starting to actually use the QR code thing, which was everywhere in like 2005. And 1seg? That was really fun tech. TV on my morning commute was truly like living in the future.
For iconic phones, though, I was always a big fan of the au Design phones like the infobar (2003) and Design Skin. The color schemes are legendary.
Since China banned imports of waste, Japan has been working on improving recycling capabilities at home. They collect something like 86% of their plastics properly sorted and are developing new more readily recyclable plastics. We should follow their lead.
The only lobbying I've heard of is against the narrow focus of BEV-only[1] policies and to include hybrid, HEV, etc. What other lobbying are you referring to?
1: https://www.energy.senate.gov/services/files/E2EA0E4F-BAD9-4...