Programming thread

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
clever handle said:
I think a sign that I'm getting old is that I seem to be moving back towards physical stuff. I can't seem to stop buying whiteboards. I buy another whiteboard, telling myself that I'll erase the stuff on it as soon as I finish the thing I'm working on, but in order to finish that thing, I have to code another thing it's dependent on, and I don't have enough space on my whiteboards, so I buy another whiteboard. I'm up to four whiteboards and am trying not to buy a fifth.
Click to expand...
I've always appreciated the physical act of pacing to drive thinking. I live in an urban area and my house has a roof deck, so for that reason so like every day I pace up there thinking about the programming / social / political problems on my mind while smoking shitty cigars.

I also conceptually love white boards, but in practice, mine are all magnetic too so I've stuck shit to them that I don't want to take down.

I think I sorta prefer sticky notes and sticking them all over my walls, and I've got a magnetic notepad on my fridge.

I think the dearth of shitty note taking and reminder apps has kinda forced me to recognize the monopoly the physical world has on my senses. Maybe some dev fucked up their notification system but with notes, I will be physically incapable of remembering I need to pick up melatonin next time I go to the store because I have it written on my fridge.
 
Marvin said:
I've always appreciated the physical act of pacing to drive thinking. I live in an urban area and my house has a roof deck, so for that reason so like every day I pace up there thinking about the programming / social / political problems on my mind while smoking shitty cigars.
Click to expand...
Ditto, I'm a bigtime pacer, I also like taking walks specifically without my phone on me. I think we've forgotten how to be bored, and along with it, the benefits that spending time in the Default Mode Network actually has. We've so optimized idle time out of existence, that we've fooled ourselves into thinking that the shower is the only place where you can be slapped in the face by genius and diffuse thinking.

And yeah, the fact that digital information can be compressed out of physical existence is a blessing and a curse, I sincerely think that peoples' lack of reliance on physical media is a huge part of why so many zoomers have convinced themselves they have ADHD. Projecting your needs and relevant issues into the physical world is useful for all sorts of reasons. Beyond being good for the memory and serving as a constant reminder, having your work space littered with programming stuff, at least for me, helps my self-image a bit, as weird as that sounds.

Also, there's just something viscerally cathartic about striking off/erasing something you're finished with. I think this is the sort of satisfaction people talk about when they say that turning pages in a physical book is more satisfying than on a phone or Kindle, even if it is less spatially-efficient.

people who insist on vinyl are still pretentious as fuck though
 
Creative Username said:
i'm fine enough with some text files scattered around on my hard drive

still love pacing and just being able to think though
Click to expand...
Oh, yeah, don't get me wrong, I still keep plenty of notes and Github issues and stuff to sorta mark out the broad strokes of what I wanna get done, long term goals, structural spec, all that stuff definitely has its place, the physical stuff is mostly for crunchier short-to-medium-term implementation details and making it easier to catch back up to what I was thinking, why X is the way it is, that sort of thing.
 
DavidS877 said:
While I don't think the code made it to github as it was an internal project, I'm pretty sure that's too much information to share on this horrible doxxxxxing site.
Click to expand...
I've refrained from linking my GitHub here (obviously) but barring something really obscure you most likely won't dox yourself
 
Does anyone else ever wrestle with a sort of naked anxiety about the stuff they make being fragile? I've at this point built out a few things I'm using in my project, but I have this weird compulsion not to test them too hard for fear that they'll break, or that the thing I made underneath them will break, etc etc.

I think it's probably just apprehension about my own skill or my ability to fix the problem or finding out that I built something on a broken premise, but I'm curious if you guys have any experience like this.
 
clever handle said:
Does anyone else ever wrestle with a sort of naked anxiety about the stuff they make being fragile? I've at this point built out a few things I'm using in my project, but I have this weird compulsion not to test them too hard for fear that they'll break, or that the thing I made underneath them will break, etc etc.

I think it's probably just apprehension about my own skill or my ability to fix the problem or finding out that I built something on a broken premise, but I'm curious if you guys have any experience like this.
Click to expand...
If you're not breaking your shit in testing, you're not doing your job right.
 
rando[Numbers] said:
Learn to draw UML diagrams, architect out even small personal projects. Use AI to ask about "architectural concerns" to help draw UML’s.
Click to expand...
Either of those sentences would, by itself, be worthy of a death sentence. UML is like flowcharts, but somehow even worse because it's tied to the OOP cult.

Creative Username said:
also what you're talking about might not fit the typical definition of "microservice": afaik it means "unix domain socket or something that runs imagemagick or whatever when you shit a file into it"
Click to expand...
A microservice is, pretty much by definition, a thing that should be a statically linked library but instead requires you to design your program around sending SOAP or REST requests via HTTPS to a server run by a startup with questionable competence, a questionable life expectancy, and billing policies that could increase dramatically at any point in the future. This means everything is slower, since every use of the "service" now means a round trip over the Internet, that any of the microservice company's data breaches are now potentially your data breaches, that any of the microservice provider's downtime is now definitely your downtime, and that in general you are now at the mercy of some Web 2.0 sociopaths whose only goal is to have their company be acquired by a larger, even less scrupulous company like Google or Oracle. I don't know why anybody would build this into one of their programs voluntarily.
 
clever handle said:
Does anyone else ever wrestle with a sort of naked anxiety about the stuff they make being fragile?
Click to expand...
No. Most of my projects from the last decade are fragile as all get out and will break if you look at them wrong. Thing is, they're written to perform a job. They don't fail me. Ever. Yeah, you can break them easily. Who cares? They do what they're supposed to. But I mean, these are projects with a user base of me. If someone came by and complained about a bug, I'd think about patching the problem for them.
 
clever handle said:
Does anyone else ever wrestle with a sort of naked anxiety about the stuff they make being fragile? I've at this point built out a few things I'm using in my project, but I have this weird compulsion not to test them too hard for fear that they'll break, or that the thing I made underneath them will break, etc etc.

I think it's probably just apprehension about my own skill or my ability to fix the problem or finding out that I built something on a broken premise, but I'm curious if you guys have any experience like this.
Click to expand...
sometimes i break my code or recognize an issue when i carefully read it
i then either ignore it because i can just not do the thing that makes it explode
or i go ahead and fix it

and remember: if you don't test your code and find the weaknesses, it will still have the problems; you might just not know about them until they are triggered at an inconvenient time
clever handle said:
True enough. I need to be a little more aggressive about stress-testing it and have some faith that my work is a few revisions away from being airtight. Should hopefully come with a few more months/years of work.
Click to expand...
write some unit tests and shit
maybe also learn about fuzzing because fuzzing is a particularly based testing method
Unimaginative Username said:
Either of those sentences would, by itself, be worthy of a death sentence. UML is like flowcharts, but somehow even worse because it's tied to the OOP cult.
Click to expand...
i have never heard of people using uml as more than a joke in the software engineering spheres i frequent
 
Creative Username said:
that enterprise java uml software engineering diagram brainrot mongoloid nocoder nigger monkey has been sperging on my profile
he also just followed me
Click to expand...
I guess I'm in good company, then. He's going through my post history and turning it into his own designated shitting street by voting every post as "Dumb", presumably because he's threadbanned for 2 days and can't reply. I object to living in his head, even if it's rent-free, because the place reeks of body odor and turmeric.
 
Unimaginative Username said:
I guess I'm in good company, then. He's going through my post history and turning it into his own designated shitting street by voting every post as "Dumb", presumably because he's threadbanned for 2 days and can't reply. I object to living in his head, even if it's rent-free, because the place reeks of body odor and turmeric.
Click to expand...
new development: i've learned that he isn't actually indian, he's just a piratesoftware alt
he's using the swebok shit as a cope for how badly his gamemaker slop is going
hopefully he will one day learn that uml diagrams won't save heartbound
 
Creative Username said:
i have never heard of people using uml as more than a joke in the software engineering spheres i frequent
Click to expand...
One of my earliest and worst experience with Pajeets is that we got one for our "Software Design" course in my undergrad. It was focused on UML. No one could take him seriously. That was his one semester at my university. If there was merit to be had in UML, I may never discover it. Sure didn't from that course.
 
UML:
- Gay
- Retarded
- Object Oriented

Bullet Point List:
- All the features of UML
- It's just a list, so it's literally a Lisp
- You can change the format to suit your needs, more flexible than UML, draw arrows
- Multi-Paradigm
 
Private Tag Reporter said:
UML
Click to expand...
maldavius figtree loves uml because he has a compulsion to open mspaint and draw boxes every 2 seconds
Private Tag Reporter said:
Bullet Point List:
- All the features of UML
- It's just a list, so it's literally a Lisp
- You can change the format to suit your needs, more flexible than UML, draw arrows
- Multi-Paradigm
Click to expand...
this is the chadliest program specification method. you just shit out a few paragraphs explaining what the fuck is supposed to be going on and then write a list of things that the program should do that may or may not be oddly like pseudocode
 
It's always weird when I finish working on something, because it seems like the space separating "deep in it, the end is nowhere in sight" from "totally done" is always much shorter than I think and seems to slam into me all at once. What's worse, it's almost like finishing up something I've been working on for weeks at a time gives me some expectation that there should be some kind of fanfare, but in reality, it's just another round of hitting F12, except this time the errors don't happen. Finishing work on something is more of a lack of stimulus than a stimulus unto itself, and I still haven't gotten used to that.

Still, today I think I finished working on this asynchronous initialization/dependency finder thing I've been working on (basically I overreacted to the potential threat of race conditions and wasted two months on some bullshit). I still need to implement it across my project and get everything rewired to use it. Not entirely sure yet if it was worth it or even necessary, but hey, I feel kinda satisfied and I learned a lot.
 
clever handle said:
It's always weird when I finish working on something, because it seems like the space separating "deep in it, the end is nowhere in sight" from "totally done" is always much shorter than I think and seems to slam into me all at once. What's worse, it's almost like finishing up something I've been working on for weeks at a time gives me some expectation that there should be some kind of fanfare, but in reality, it's just another round of hitting F12, except this time the errors don't happen. Finishing work on something is more of a lack of stimulus than a stimulus unto itself, and I still haven't gotten used to that.

Still, today I think I finished working on this asynchronous initialization/dependency finder thing I've been working on. I still need to implement it across my project and get everything rewired to use it. Not entirely sure yet if it was worth it or even necessary, but hey, I feel kinda satisfied and I learned a lot.
Click to expand...
It really depends on what kinda project it is. For example, in business software, a lot of the time you have to do many rounds of "done" because of wrong specs and such.
 
You must log in or register to reply here.
Back
Top Bottom