>I wonder if we need better programming abstractions/ languages that can make programming easier for people.
That was nodejs, and it turns out people unwilling and or unable to improve things through systematic skill refinement just degrades into chaos.
Successful ecosystems are just pedantically lame enough to keep silly folks from going YOLO, but empowering enough to allow people to still have fun.
>which model has the best training code that was Pac-Man.
You mean which model is more cautious about copyright bleed-through of the $9Tn in FOSS and user code they misappropriated though isomorphic plagiarism. =3
There is a difference between risk mitigation, and remote administration tools. The risk of stealing from competitors with a backplane monitoring system may not end up forming the desired control asymmetry.
The hidden agent risk in LLM often can't be detected during training and evaluation. =3
Usually the university takes half of any funds, faculty takes half, and whatever is left over is split between the associated academics.
You were lucky, as most university contracts clearly state they own all associated IP created while working on campus. They could have legally given you $0, and end of employment notice. These things can get messy fast. =3
Yep. I was on a fixed term contract, which had expired, even though I was still working on the project well after its expiration. It would have been interesting to argue that any IP assignment expired with the contract. As you said: messy. As I judged: not worth it.
In general, most founding staff with lucrative contracts, are often pushed out just before an IPO. Doesn't matter if you were friends, worked 60 hour weeks building the company for years, or name is on the company patents.
A bit of cash can turn folks into awful people, and some contracts are just a obfuscated legal con of the naive. =3
I'm just differentiating between the legal correctness and personal opinion/viewpoints on the matter.
Regardless of whether you are legally correct or not isn't really the crux of the issue for me, heck maybe Jensen doesn't even care about a billion given everything's he's minting (who knows though).
I was only talking from personal standing, in your stated cases or if I was in this position (I made some assumptions regarding the case), it would be a breaches of good faith and I would find it hard to trust them in a partnership ever again.
Only my POV, maybe the folks at the B level don't care about this as much since they are starting to fling Ts around. I can see how some people wouldn't really care, i.e. treating them as a freelancer and main objective is getting something done, but on a personal basis probably wouldn't trust them (say on personal matters that are company defining).
In production, Go has proven solid for several years. It is best when used with the native code people ported.
There are only two issues I encountered:
1. getting the legacy ancient C source meta-circular Go compiler working to port the Go boot-strap compiler upgrade chain is a kick in the pants. However, once it is on a architecture it has proven rather resilient.
2. memory limited systems can develop reliability issues, as Go programs will often ungracefully throw hard to diagnose unrelated errors during each crash. A good metric is 3:1 of your average load as a safety margin (if you see 2GiB in average RAM use, make sure to over-provision the host with 8GiB RAM etc.)
Other than the above short list of edge cases, if you join a pure Go project it is usually pretty reliable. Most community folks interested in the language seem fairly competent at building stuff that is fun. =3
I found Go memory issues easier to solve than Java issues. You can see an example with etcd used in Kubernetes. I had to enable performance profiling in etcd to identify why it was eating up all the memory. It led me to a specific partition of keys that tracked back to a specific object type in Kubernetes.
It was literally enabling a flag and running some commands to do some really quick exports.
Dealing with the JVM though, heap dumps are slow to process and the UI I had to download was very clunky. I don't know if there are better tools, but even if there are the path to just doing it isn't straight forward.
Observability on the JVM is second to none, especially with tools like JFR available for free. You can literally connect to a live JVM and introspect it.
Not sure why your opinion was buried, but Java Applets in the wild are rare these days. There is little Java offers not already covered by HTML5, wasm, and WebGL. Only naive student projects, and legacy systems cling to the ecosystem.
>state of the art GCs
That just isn't true, most of the Subscription Enterprise Performance Pack features are under a paid license by Oracle. The FOSS options are always slowly catching up, or not standards compliant enough for some commercial programs.
Being a sentient turnip, I probably wouldn't understand such things. Yet in general, 3rd party dependency injection into a design pattern should be considered a long-term variable cost. =3
Rule #3: popularity is not an indication of utility.
Copy Microsoft backward-compatibility focus, Apples aesthetic choices, and media/game-engine API definitions.
Open desktops are like an architect that keeps moving the bathroom doors in a building under perpetual construction. The ecosystem naturally destroys itself every major release cycle, work put into quality of life improvements is lost, and code smell is so terrible people just abandon the projects after it becomes burdensome.
The mistake people make is trying to reason with people about which groups breaking changes take priority. This is why Cinnamon continues to run desktops on systems with broken GPU drivers, and installed as a fail-back GUI plan when Wayland glitches up.
People need to stop telling new users to follow a 15 step CLI tutorial to bring up a broken distribution Desktop. =3
If you live in New York, life will get complex without building supplementary passive income from a young age.
If people live a slow-burn lifestyle, buy revenue property one can later demolish as needed, park unused cash in index funds, and split 7% between bullion & high-risk. Most folks will be fine when things eventually go sideways.
Some people like to gamble, but they usually don't talk about their mistakes. =3
I am not Bullish on LLM firms given the -$2.50 profit per $1 revenue, or several trillion USD debt buried on page 60 of their reports. They can go be awesome without my cash, and I will cheer them on.
Note, whomever floated that home-equity loan will be happy with their won profits. They win-win even if the loan defaults. Not everyone is so lucky... =3
Joel Spolsky lived and worked in New York, so opinions were heavily influenced by the reality of east-coast economics.
My comment was advice that most people will learn the hard way, and hopefully inspire a moment of pause about their own risk exposure tolerance.
The subject is about young workers that acknowledged the very real churn part of the ephemeral tech sector, and position themselves for an early exit strategy into adjacent careers or retirement. This is not a new idea, given vertical movement in software careers has been stagnant for decades. =3
Mostly seeking design tips for a vacuum tolerant micro-positioning stage project. =3
reply