The OFFICIAL programming thread
-
@Gators1 said in The OFFICIAL programming thread:
@Kilemall said in The OFFICIAL programming thread:
@Gators1 said in The OFFICIAL programming thread:
Can someone do this and train it with LOT posts? I am too lazy to watch a 5 hour video let alone do the programming.
There are treaties against LOT derived AI.
Fuck the treaties! We will make billions!
Maybe as Bond villains.
-
@Gators1 said in The OFFICIAL programming thread:
Can someone do this and train it with LOT posts? I am too lazy to watch a 5 hour video let alone do the programming.
My favorite video creator does game dev tutorials that run between 30 seconds and 5 minutes. I love that guy. Five hours is a no from me.
-
Great line from Larry Wall, creator of Perl (which I’ve barely used) on Java:
“If 100 lines of Java code accomplishes a task then it looks like you’ve written 100 lines even though in a different language it might only take 5 lines. You can eat a one pound steak or you can eat 100 pounds of shoe leather and you feel a greater sense of accomplishment after the shoe leather but, you know, maybe there’s some downsides.”
-
I so want to reply, “You made all those names up, didn’t you?” But, sadly, Stack Overflow has no sense of humor
-
Learning new programming languages is somewhat like having been in a accident and having to learn to walk again (without the physical pain of course). Some languages are more familiar than others and you can get basic movement going again relatively quickly although it can take a long time to regain the finesse you had. Some languages are kind of familiar but have some alien ideas and just learning to move in them takes time and practice. They’re more frustrating but eventually you get there.
Learning Common Lisp is like having had an accident that involved a time machine and going back to the 1970’s. Except in another dimension. For some reason, in this dimension, learning to walk requires you to operate an 8 track tape deck, a rotary phone and a vintage wheel balancer - none of which you’ve used before. Oh, and everyone speaks some weird dialect of Esperanto. You kind of recognize bits and pieces but it’s largely alien.
-
It’s pronounced “lithp”.
-
-
This is why Indian videos are my favorite for coding advice… I thought this was a parody at the start.
-
@Gators1 I lasted 30 seconds before it triggered my PTSD from I dunno how many teams meetings I’ve had.
-
@Hog when AT&T bought my company in PR, we had meetings with their team to coordinate bringing our data to their systems. The guy that managed our database stuff had no fucking idea what they were saying. He would sit on the call for an hour, then come to me and ask if he had to do anything. I work with a bunch domestically and they are pretty good, but dealing with the offshore companies is painful.
-
@Gators1 said in The OFFICIAL programming thread:
@Hog when AT&T bought my company in PR, we had meetings with their team to coordinate bringing our data to their systems. The guy that managed our database stuff had no fucking idea what they were saying. He would sit on the call for an hour, then come to me and ask if he had to do anything. I work with a bunch domestically and they are pretty good, but dealing with the offshore companies is painful.
Are they paradigm buzzword posers?
-
-
So I need to write my code in such a way that even GPT can’t understand it and I’m the only one who knows how to maintain it?
Challenge accepted.
-
@Hog said in The OFFICIAL programming thread:
So I need to write my code in such a way that even GPT can’t understand it and I’m the only one who knows how to maintain it?
Challenge accepted.
Given how bad a lot of the code i see is, I wonder where they found enough of the good stuff to make a training set?
-
@Hog said in The OFFICIAL programming thread:
@Gators1 I lasted 30 seconds before it triggered my PTSD from I dunno how many teams meetings I’ve had.
keep in mind the advice i took to heart years back: the only meetings worth attending are the ones that cannot start without you.
-
@oyaji said in The OFFICIAL programming thread:
@Hog said in The OFFICIAL programming thread:
@Gators1 I lasted 30 seconds before it triggered my PTSD from I dunno how many teams meetings I’ve had.
keep in mind the advice i took to heart years back: the only meetings worth attending are the ones that cannot start without you.
That would probably be half of them. Meetings these days are different to what they used to be. For me at least. They are much more focused, shorter and less formal. Most are scheduled for half an hour but often wrap in 10 to 15 minutes if the reason for the meeting has been addressed. I have more meetings now than I ever had but they are a lot more productive. Maybe it’s just because we are all working remote and spread over several countries. If we were all working in the same office space we’d probably just huddle around someone’s desk for most of them.
-
Someone in a Hacker News thread mentioned “Kernigan’s Law” which I’d never heard of. I googled it expecting to find something insightful and profound. Instead I got this:
I’ve said the same thing in various forms* for decades, dammit. I want to be the first in a field for a change so when I say some stupidly self evident shit, they call it Hog’s Law and put it in text books.
(* I used to teach coders that, even when you’re coding solo, you’re part of a team. It’s just that that team is distributed through time. So make your code readable and maintainable because that other future team member might be you.)
-
@Hog said in The OFFICIAL programming thread:
@oyaji said in The OFFICIAL programming thread:
@Hog said in The OFFICIAL programming thread:
@Gators1 I lasted 30 seconds before it triggered my PTSD from I dunno how many teams meetings I’ve had.
keep in mind the advice i took to heart years back: the only meetings worth attending are the ones that cannot start without you.
That would probably be half of them. Meetings these days are different to what they used to be. For me at least. They are much more focused, shorter and less formal. Most are scheduled for half an hour but often wrap in 10 to 15 minutes if the reason for the meeting has been addressed. I have more meetings now than I ever had but they are a lot more productive. Maybe it’s just because we are all working remote and spread over several countries. If we were all working in the same office space we’d probably just huddle around someone’s desk for most of them.
The technical problem solving huddle is waaay more efficient in person, and a dead letter in IT I suspect.
-
@Kilemall said in The OFFICIAL programming thread:
@Hog said in The OFFICIAL programming thread:
@oyaji said in The OFFICIAL programming thread:
@Hog said in The OFFICIAL programming thread:
@Gators1 I lasted 30 seconds before it triggered my PTSD from I dunno how many teams meetings I’ve had.
keep in mind the advice i took to heart years back: the only meetings worth attending are the ones that cannot start without you.
That would probably be half of them. Meetings these days are different to what they used to be. For me at least. They are much more focused, shorter and less formal. Most are scheduled for half an hour but often wrap in 10 to 15 minutes if the reason for the meeting has been addressed. I have more meetings now than I ever had but they are a lot more productive. Maybe it’s just because we are all working remote and spread over several countries. If we were all working in the same office space we’d probably just huddle around someone’s desk for most of them.
The technical problem solving huddle is waaay more efficient in person, and a dead letter in IT I suspect.
Yeah maybe. I’m lucky that the people I work with in an average week are in Sydney, Melbourne, Perth, Singapore, Jakarta and various cities in the Philippines and India so there’s no pressure to get us into the office for efficiency gains (real or imagined).
-
I wrote this thing early last year that was probably one of the most challenging greenfield developments I’d ever done (it’s usually only supporting other people’s code that is particularly challenging). I had to learn a bunch of new tech for this thing and I had to rearchitect it twice before I got there. Anyway, when it was done, it was clever, elegant, easy to use, well coded and well documented. I admit that months after it went live, I still read through the docs from time to time just to remember and enjoy what I had created.
However, after a recent upgrade, it was discovered that:
a) this thing I’d made was now causing intermittent problems with another process.
b) the problem that led to the thing even being developed in the first place no longer existed.I more than happily recommended that we just delete the thing I made. I got paid for it, I enjoyed making it and, even though it hadn’t created a single issue before now that required my attention, deleting it means I never have to support it again. It’s like win, win and win.
Create a Large Language Model from Scratch with Python – Tutorial
