I started a master's in ecology with the hope of doinh a PhD after. Academia honestly sucks and has pretty bad culture issues (and like 10% of the pay) but I genuinely really like animals and it feels good to have my job be helping them.
Personally I don't think I would recommend it. Not that it's necessarily a bad choice but I think that the people for who this is the right choice will feel compelled to make a change regardless of what I say (I know I had people trying to convince me to stay in tech). Fully changing careers like this and living the poor and overworked grad student life in my 30s has taken more commitment and stubbornness than I had expected but some fights are worth doing.
It work on the dirt-bike tier e-bikes because they can get away. IF they are walking my child has been harassed by Karens asking "why they are out on their own." I look forward to the day they are old enough to ride a fast enough e-bike to escape people with cell phones that will rat them out for being out and about.
I largely blame cell phones for the Karens being able to impose their will. When I was a kid we were all out about and/or doing dumb shit, but anyone who wanted to call the authorities had to go home to find a telephone. By that time we were long gone. As long as we didn't go near houses, no one could touch us. Now they will just follow the kid with their cellphone until the rat-fuckers from CPS or the police arrive.
We tell children not to talk to strangers but if a random adult goes up to a child and says something like "Why are you out on your own," what are they supposed to do?
Thankfully this never happened to me as a child, I don't even know what I'd do.
In fact auto-complete in VS code with copilot works surprisingly well. Let’s say there are patterns in how classes in a framework are constructed, and I already added changes to the schema, it will often emit the correct implementation code when going there. That is really speeding me up even if I know the code base very well.
The harder part is understanding the nature of the data you're working with. There's always some catch ("oh that field `foo` was never backfilled, so for queries before 2020 you have to recompute it by joining with legacyBar instead")
> SQL is not hard enough to require an LLM to think about for you
As someone who's seen queries that are hundreds of lines long, involve a bunch of CTEs, nested SELECTs as well, upwards of a dozen joined tables with OTLT and EAV patterns all over the place (especially the kind of polymorphic links where you get "type" not "table_name" so you also need to look at the app code to understand it), I'd say that SQL can be too hard for people to reason about well.
Bonus points for having to manually keep like 5 Oracle package contents in your working memory cause that's where the other devs on the 10 year old project stored some of the logic, while the remainder is sort-of-dynamic codegen in the app.
Same as with most app code, it shouldn't be like that, but you sometimes get stuff that is really badly developed and the cognitive load (both to inherent and accidental complexity) will increase until people will just miss things and not have the full picture.
Not sure why you are getting downvoted. I don't think an artist would "one-shot" an art piece, let's say an image. At what point of the iterative process does the output become "Art"? What if the artist makes it a point to one-shot images and the ugliness of the output becomes their commentary of the current aesthetics...
I'd say it's much more about intent than the process, there are plenty of "Artists" on instagram (in quotes because I would not consider them artists), who paint by hand, surely talented people, but their images convey nothing. They are clearly marketing/branding themselves, the instagram post becomes the actual final output...I don't know.
And it could easily have been 10 KB.
reply