XBOX is short for XBox One X
GNU is short for GNU Not Unix
😲😱
Recursive Definitions

That moment when you make your code such that even dummies can understand it, implement smart ass algos, do all those comment line things for definitions. Then you show your project to your teacher who has this to say :
"Why are you showing me copied code?"
I am like

Having PHP as my most useful skill.

I know various other languages, but they're either too exotic for professional use, or my knowledge about them doesn't have the same depth as with PHP.

People joke about how awful PHP is, and it's not entirely true. The incongruous stuff such as confusing parameter ordering can be fixed with libraries. And PHP7 fixed a lot of the ugly stuff. A good dev can certainly write structured, readable, performant PHP code.

But there is a real hard limit. PHP is missing more complex type definitions present in other languages. A weak type system is like building stuff with popsicle sticks and bits of duct tape, it works fast and perfectly fine for small projects, but the lack of strictness is a problem when you have thousands of classes intertwined in all kinds of complex factory, service and repository patterns. And the simple type hints are still newish and fully optional, which means a lot of people don't use them.

So I regret getting stuck in this self reinforcing loop, where I learn more about a very imperfect language through employment, and keep rolling into jobs using that skill because it's what I'm most experienced with.

This happens so often!
*Lecturer teaching using a ppt*

A slide with literally one basic understandable sentence on it : unnecessarily discussed for 20 min.

A slide with actual important stuff,graphs, definitions charts etc. : Skipped in 5 sec 😑

"Kiki, I want you to, for the first time of your career at %company%, quit worrying about deadlines and just wander free. Forget about due projects, forget about everything, and just do your crazy experiments till the end of this month."

This was the one-to-one with our CEO today. Yes, I'm being paid to do whatever I want without time restrictions, as long as it is related to my field.

And you know what? At this stage of my life, I don't even want to exploit that, to weasel my way around definitions and justify doing nothing. I legit have three AI experiments to run, I have money to run them, I have time, and I for sure have motivation.

Good workplace is when doing nothing isn't the most desirable thing to do.

This is happening in Firefox. The definitions are not being rendered.

TeamLeader: I need you to stop disagreeing with the decision of the management, the people in there are taking their decision for a reason.

IHateForALiving: When integration tests were failing, the management decided to comment out the ingration tests; god knows how many bugs slipped by.
When users had problems with the idiotic migration process the management designed, the management decided to remove down migrations; it took two weeks before the QA team started screaming, as all their machines were filled with garbage data.
I was writing type definitions for my code, you removed it. You effectively ensured the only person capable of working on that particular piece of code would be me.
I have been proposing for 8 months to make a unified scheduled jobs system, you all decided to create at least 5 different -and incompatible- implementations, at least 4 of them are total garbage with setTimeout, there's no way to ever unify them and God willing they never break, if they do there's NO WAY to find out even where tf they're hidden in the code.
Every time you were making one of those bad decision I was the only one warning you of the problems you were creating. The idiotic change of the day is going MongoDB+Angular: I can keep a low profile if you want, but when this blows up you can be damn well sure I'll handle my 2 weeks notice because there's no way on earth I'll be stuck with the aftermath of you lot taking technical decisions you are clearly unable to manage.

IT Definitions of Designations

Project Manager is a Person who thinks nine women can deliver a baby in One month.

Developer is a Person who thinks it will take 18 months to deliver a Baby.

Onsite Coordinator is one who thinks single woman can deliver nine babies in one month.

Client is the one who doesn't know why he wants a baby.

Marketing Manager is a person who thinks he can deliver a baby even if no man and woman are available.

Resource Optimization Team thinks they don't need a man or woman; they'll produce a child with zero resources.

Documentation Team thinks they don't care whether the child is delivered, they'll just document 9 months.

Quality Auditor is the person who is never happy with a delivered baby.

Tester is a person who always tells that this is not the Right baby.

HR Manager is a person who thinks that...a Donkey can deliver a Human Baby - if given 9 Months

So, I just realised that a contribution I made to an open source project 12 days ago had gotten accepted 3 days ago. I'm so ecstatic over this!
I was basically just in need of type definitions for a javascript library, and seeing as it didn't have any, decided to make them myself. Done that, I made a pull request, but seeing as there was no changes after a few days, I forgot about it.
Now I just remembered about that, and wondered if it got any comments or anything, and it turned out that they had accepted my PR and it had already been put into a release 3 days ago
I can't contain myself right now, it was my first open-source contribution, and it just feels good to know that I somehow helped some people by giving them type definitions :D

Cheers

Update on my old rant: I started writing type definitions for our project (it's basically a chunk of separate files where you document the objects you use; typed languages have this out of the box, js doesn't and it may become useful depending on the size of the project). Our codebase is reasonably big -not complicated, but big- and I felt like I was losing track of all the properties\objects\usage\comments\whatever. So I iiterally wrote some ts interfaces: properties with name and types, that's it, so you know what you're passing around.
Proposal was denied, I'll have to delete the documentation; "keeping the doc updated is going to require more work".

Me: Ok, but what am I supposed to do when I need to interface with your code? Run the debugger and figure out what the fuck you guys are passing around?
Team leader: Yes 😊

Teaching my little sister Mathematics (Grade/Class 12. Not at all easy).

And I can really understand the textbook definitions in the chapters. Back then, I never understood a single line of it.

Am I a more sound mathematician now or reading poor documentations has improved my skill to read complex and minimal contents!

I'm not sure is it a container technology or a zoo...

Docker is Whale
Docker Compose is Squid
Podman is Seal
Linux is Penguin

Are we live in the Arctic?

trying to do anything on the PS2 is almost fucking impossible

i imagine a board meeting where they were designing the hardware

"how can we make this insanely hard to use?"

"let's make decentralized partition definitions, allow fragmenting of entire partitions, and require all partitions to be rounded to 4MB. If you delete a partition, don't wipe the partition out, just rename it to "_empty" and the system will do it for you, except it actually won't because fuck you"

"let's require 1-bit serial registers to be used for memory card access and make sure you can't take more than 8 CPU cycles to push each bit or it'll trash the memory card"

"let's make the network module run on a 3-bit serial register and when initialized it halves the available memory but only after 8 seconds of activity"

"let's require the system to load feature modules called "IOPs" and require the software to declare which of the 256 possible slots it wants to use (max of 8 IOPs) then insert stubs into those. Any other IOP you call will hang the system and probably corrupt the HDD. You also have to overwrite the stubbed IOPs with your own but only if you can have the stubs chainload the other IOPs on top of themselves"

"let's require you to write to the controller registers to update them, but you have to write the other controller's last-polled state or the controller IOP will hang"

of course this couldn't make sense, it's

s s s s
o o o o
n n n n
y y y y

LabVIEW.

Because WHY THE ACTUAL FUCK should you want to use a visual programming language in a professional environment and pay for it.

(Other than: the manufacturer of your measurement device/power supply/electronic load/etc. has already provided a LabVIEW module so you just have, you know, 'click' your program together and be done.

No, we won't give you the documentation on how to do it properly without that piece of crap or even give you code snippets.

(If you don't feel the urge to shoot yourself in the foot, you have obviously too much time on your hands and could simply be reading the interface definitions for that particular interface. At least it's standardized, d'uh.)

Oh, and you want a lightweight application? Here comes the runtime environment! A big clunky ... thing you'll need now to start up even a simple measure-and-log-data-thing.

Well, OK, it works for the occasional Measure-and-Log-Thing. If you don't need the data too fast.

If you want to do something a bit more complex, knock yourself out, but don't ask me to debug it for you afterwards because that colourful entanglement of wires and connections and blocks is a DAMN HUGE MESS and trying to understand how it works feels like defusing a bomb in a shitty action movie.)

Never again.

Something I've noticed over my many jobs. "Professional" means entirely different things at different jobs, and doesn't follow fields either. That is, "Professional" in one field is understandably different from another, but businesses inside the same field also have different definitions of it.

It's almost as if "Professional" is just a euphemism for saying "we expect you to act a certain way, but are being passive aggressive about it so we can't be called out for it".

Code fuckup day or what?! After two weeks where I wasn't on my project and a co-worker handled it, I came back to my project and reviewed what he had done so far.
Me: "I don't understand how this new code part here can work?"
Him: "Uhm, actually, it doesn't, somehow."
Me: "..."
Then he had checked in his stuff with spaces while the whole project is with tabs. And variables that were used in a different way, but still under the old name, now completely misleading. Bypassing existing infrastructure and defines with "just for this case" hacks. But the best was tracking higher level state by peeking into lower level data buffers, even pulling out their data definitions into global header files - instead of using proper states in the higher layer itself.
NOT! IN! MY! FUCKING! PROJECT!!!
So I spent the day cleaning up the shit to fight off software rot right in the beginning.

> testing cronjob
> * * * * * /script.sh
> CPU spike to 100% all time

*FU#K*

*Outsourcing DevOps Company*

> HR got a call from a customer
> Got my contract terminated immediately
> HR and my boss trying to explain to me about the situation
> The customer is one of BIG GIANT conglomerate in my country and high expectations AF
> My boss wants me in the team
> HR denied due to headcount and limited budget from investors
> CEO pay me for the whole 2 months in salary in compensation including unused vacation under the national labour law right away after signing an acknowledge form
> HR told me if I go to the new company, don't forget to tell them about referring

This all happens under 30 minutes after a normal working friday

What a shock

PS. It's a nice DevOps outsourcing company in both working culture and technical TBH

HTML & CSS.

To me they just feel wrong.

I have been working with them for a little over 20 years now, and it feels like very little has improved. Sure we learned to make things look a bit nicer, we got new tags and properties, but the syntax is still horrible.

The fact that both are replaced by other imperfect languages (haml, jade, less, sass, etc) is just a confirmation that their paradigms are about as fucked up and impossible to exterminate as cobol.

Which points at another problem: browsers, and how slow the web upgrade cycle is — adding native support for nested style definitions in css, or replacing html with a json document seems like a trivial problem, if it weren't for the dozens of browsers and the excruciating pace at which they can adopt standards.

I may not be a dev... (learning in my off time though, best thing ever) but I have been responsible for the computer system validation, requirements definitions and planning of a new piece of software that will have a major increase in effeciency for a division consisiting of over half our companies employees.

For months it has been a painful process. I have had night terrors, immense pressure on my head all the while thinking we are getting to that final goal (live deployment), and the light at the end of the tunnel has just seemed to be getting further and further away... Like a donkey chasing a carrot on a stick.

After all the grey hairs, stress and drinking I am finally going to deploy this thing to the live environment tomorrow. Funny thing is its the part of this process that managers are stressing about and I am here like... Oh wow my Friday just got a whole lot better

Dev: We have a data quality problem. Combined with data silos, we can't trust the numbers. We need to agree on metric definitions as a company.

CTO: (Points a PM)Help him on the metrics he has defined. We'll discard any other alternate definitions inside the company.

PM: You can start with these. (Throws a bunch of metrics without their definitions. Doesn't respond to questions regarding definitions.)

After a week of generating aggregates,

PM: The numbers seem wrong.

Fuck I know the numbers will be wrong. Because you didn't give me the definitions and I'll have to deduce them myself.

Seriously guys, how do you deal with PMs who don't cooperate in the requirement analysis?

Okay so my brother in law has a laptop that is... To put it mildly, chockful of viruses of all sort, as it's an old machine still running w7 while still being online and an av about 7 years out of date.

So my bro in law (let's just call him my bro) asked me to install an adblock.

As I launched chrome and went to install it, how ever, the addon page said something like "Cannot install, chrome is managed by your company" - wtf?

Also, the out of date AV couldn't even be updated as its main service just wouldn't start.

Okay, something fishy going on... Uninstalled the old av, downloaded malware bytes and went to scan the whole pc.

Before I went to bed, it'd already found >150 detections. Though as the computer is so old, the progress was slow.

Thinking it would have enough time over night, I went to bed... Only to find out the next morning... It BSoD'd over night, and so none of the finds were removed.

Uuugh! Okay, so... Scanning out of a live booted linux it is I thought! Little did I know how much it'd infuriate me!

Looking through google, I found several live rescue images from popular AV brands. But:
1 - Kaspersky Sys Rescue -- Doesn't even support non-EFI systems

2 - Eset SysRescue -- Doesn't mount the system drive, terminal emulator is X64 while the CPU of the laptop is X86 meaning I cannot run that. Doesn't provide any info on username and passwords, had to dig around the image from the laptop I used to burn it to the USB drive to find the user was, in fact, called eset and had an empty password. Root had pass set but not in the image shadow file, so no idea really. Couldn't sudo as the eset user, except for the terminal emulator, which crashes thanks to the architecture mismatch.
3 - avast - live usb / cd cannot be downloaded from web, has to be installed through avast, which I really didn't want to install on my laptop just to make a rescue flash drive
4 - comodo - didn't even boot due to architecture mismatch

Fuck it! Sick and tired of this, I'm downloading Debian with XFCE. Switched to a tty1 after kernel loads, killed lightdm and Xserver to minimize usb drive reads, downloaded clamav (which got stuck on man-db update. After 20 minutes... I just killed it from a second tty, and the install finished successfully)

A definitions update, short manual skimover, and finally, got scanning!

Only... It's taking forever and not printing anything. Stracing the clamscan command showed it was... Loading the virus definitions lol... Okay, it's doing its thing, I can finally go have dinner

Man I didn't know x86 support got so weak in the couple years I haven't used Linux on a laptop lol.

You know you are not normal and way outside of this world when you shake your head up and down, and get convinced while you read about new definitions on existing words ON A FUCKING SATURDAY!

Frigging corporate antivirus updated its definitions and decided a class generated by Gradle on my debug builds is an infection risk. And as it's an intermediate output and it's deleted and recreated every time, it sends a new alert every time. And sometimes it can't quarantine it because it's deleted faster than it's processed by the antivirus, so it's getting a higher and higher risk level each time. And I can't add it to the exclusion list because of a permissions issue. Oh well...

Things that randomly make me sad: Python definitions always end in a sad emoji ):

So about two months ago in my consulting firm I was asked to replace a colleague on a project (node and Angular). The project is only a few months old but it’s already a total clusterfuck. DB is very poorly designed. It’s supposed to be a relational database but there’s not a trace of a foreign key or any key for that matter and I’ve seen joins like tableA.name = tableB.description (seriously, that’s your relation??). The code is a mess with entire blocks of code copied from another project and many parts of the code aren’t even used. He didn’t even bother renaming variables so they would make sense in the context they were shamelessly thrown into. The code is at best poorly typed if not typed at all.

During our dailies I sometimes express my frustration with my other colleagues as I very politely allude to my predecessor’s code as being hard to work with. (They are all “good friends" with him). I always get the same response from my colleagues: "yeah but you’ve gotta understand Billybob was under a lot of pressure. The user stories were not well defined. He didn’t have time to do a proper job". That type of response just makes me boil inside.

Because you think I have time to deal with this shit? You don’t think I’m working with the same client and his user stories that are barely intelligible? How long does it take to write type definitions for parameters going into a function? That’s right, 30 seconds at most? Maybe a minute if it’s a more elaborate object? How much time do you think you’ll save yourself with a properly typed function or better yet an interface? Hard to tell but certainly A LOT MORE than those 30 seconds you lost (no, the 30 seconds you INVESTED) in writing that interface!!!

FUCK people with their excuses! Never tell me you don’t have time to do a proper job! You’ve wasted HOURS of my time just because you were too fucking lazy to type your functions, too lazy to put just a little more thought into designing your tables, too lazy to rename a variable so that it’s name actually makes sense where it’s being used. It’s not because you were short on time. You’re just lazy!
FUCK!!!!!!

THE TYPESCRIPT DEFINITIONS SAGA CONTINUES

> IHateForALiving: so, I don't really know which field we're supposed to use here, but that's your entity I'm working on, so...
> TeamLeader2: wait, what is this? Why does your code have autocomplete?
> IHateForALiving: Every time I worked on some parts of the code I've been writing some type definitions along the way, and it's adding autocomplete if you type hint your code... but I've been told not to write them anymore, so I stopped
> TeamLeader2: But why tho? It's so fucking handy
> IHateForALiving:

My new favourite license

# The "You Can't Have It" License (YCHI)

**Version 1.0, October 2024**

**Copyright Me. All rights reserved.**

## 1. Definitions

**1.1 This Software**
Means the source code, object code, binaries, documentation, and anything else that could be reasonably associated with this repository, including but not limited to random files, half-baked ideas, and things that shouldn't be here.

**1.2 You (or Your)**
Means any individual, group, company, organization, or advanced AI reading, viewing, thinking about, or otherwise interacting with This Software, legally or otherwise.

**1.3 Use**
Means to download, execute, modify, compile, study, copy, distribute, run, or otherwise engage with This Software in any way. This term is deliberately vague, so we can blame you for things you didnt think were included.

**1.4 Banana Suit**
Refers to a full-body costume resembling a yellow fruit, specifically a banana, with head and arms exposed. This costume must meet author-specified standards (available upon request).

**1.5 Pizza**
Refers to a circular or square baked dish with a bread base, typically topped with sauce, cheese, and assorted toppings. **Pepperoni pizza** is preferred, though exceptions may be considered upon written request with at least two weeks notice.

**1.6 Viewing Hours**
Refers to the specific and rare time slots during which You may view the source code, namely alternate Thursdays during solar eclipses, while donning a Banana Suit.

---

## 2. Terms and Conditions for Use, Distribution, and Modification

**2.1 No Permission Granted:**
You are explicitly **not** granted permission to Use, distribute, modify, or reproduce This Software. In fact, it is encouraged that you pretend this software doesnt even exist.

**2.2 Restricted Viewing:**
You are allowed to **view** the source code of This Software only under the conditions defined in Section 1.6 ("Viewing Hours"). Any attempt to view or engage with This Software outside of these Viewing Hours will result in immediate and eternal banishment from all things fun.

**2.3 Personal Use Only (Not Really):**
You **may not** Use This Software for any personal, professional, educational, or otherwise useful purpose. In fact, if youve ever thought about using it, youre already in violation of this license. Apologize immediately.

**2.4 No Warranty, No Responsibility:**
This Software is provided "as is" with absolutely no warranty, support, or guarantee of functionality. If it breaks, you get to keep both pieces. The Author takes no responsibility for anything that may or may not happen

Honestly, school is useless for me as of right now. I know I should be well rounded and stuff, but do I honestly need to know the symptoms of cervix cancer while going into a tech career? My eyes have been set on tech for my whole life, ever since I left the womb, and I know that if I do switch careers, it'll be from comp sci to cyber security not from IT to med school...

I feel like I could really be devoting my time towards something better than writing a 5 page essay on a healthy food choice.

Every night I think to myself, "You know what, I'm going to lock myself in a room and write bash scripts all day" but then I wake up in the morning, and remember I have to take a quiz on reproductive systems, learn about the procedure of organ donations for driver's ed, write 2 paragraph definitions of vocab words, and read a book about communism.

The most useful thing I learned last year, was how to efficiently navigate the java API, and that's something you don't even learn, you just encounter it. Schools need to start having more specific specialties and stop enforcing knowledge of pointless topics.

I'm not saying to remove all core classes and stuff, I'm saying why waste space in our brains with something we won't use ever again? I get it, some people don't know what career they're looking for yet so you can't make them choose, but it honestly sucks some serious ass that I can't learn what I want to at school, and as a matter of fact, I can't even learn at home, because they're filling my schedule with pointless work because they feel that they have to fill our time somehow.

Point of this long ass rant is: Why lock yourself in a room and learn about something if it isn't something you want to learn about? The space in our brain is finite enough, why can't it be filled with things we're interested in rather than things that will only be used to get good grades in the future then overwritten with useful knowledge. Same thing with time. We have a very finite amount of time in a day, and now that I think of it, a lifetime. Why spend it on something that doesn't, and never will, make your life enjoyable?

Is the CS field creating terms for the sake of creating terms?

Someone mentioned a "closure" in another post. I instinctively knew what they meant by that based upon the code I saw. I had heard the term thrown around before, but it had not yet connected in my mind. I wondered why I had not been exposed enough to care.

So I thought: What does C++ have as far as closures?

I found that C++ has lambdas. Those are definitions for function objects. They do not exist at runtime. But a closure does. The analog is you have classes. They are definitions and do not exist at runtime. But instances of classes do. So at runtime the instance is what you are working with. This is the same as lambdas vs closures in C++. The closure is the runtime counterpart. Why a separate term for what essentially is an instance? Is it because it captures data and code? As far as I know the closure is all data that gets passed around that calls a function. So it is essentially an instance of a lambda.

Another term: memoization. I have yet to see this added to any dictionary in online tools like a browser. Is the term so specific that nobody cares to add it? I mean these are tools programmers use all the time.

My guess is these terms originated a long time ago and I have just not been exposed to the contexts for these terms enough. It just seems like I feel like I have been in the field a long time. But a lot of terms seem alien to me. I also have never seen these terms used at work. Many of the devs I work with actively avoid CS specific terms to not confuse our electrical coworkers. My background started in electrical. So maybe I just didn't do enough CS in college.

1) Learning little to nothing useful in formal post-secondary and wasting tons of time and money just to have pain and suffering.

"Let's talk about hardware disc sectors divisions in the database course, rather than most of you might find useful for industry."

"Lemme grade based on regurgitating my exact definitions of things, later I'll talk about historical failed network protocols, that have little to no relevance/importance because they fucking lost and we don't use them. Practical networking information? Nah."

"Back in the day we used to put a cup of water on top of our desktops, and if it started to shake a lot that's how you'd know your operating system was working real hard and 'thrashing' "

"Is like differentiation but is like cat looking at crystal ball"

"Not all husbands beat their wives, but statistically...." (this one was confusing and awkward to the point that the memory is mostly dropped)

Streams & lambdas in java, were a few slides in a powerpoint & not really tested. Turns out industry loves 'em.

2) Landed my first student job and get shoved on an old legacy project nobody wants to touch. Am isolated and not being taught or helped much, do poorly. Boss gets pissed at me and is unpleasant to work with and get help from. Gets to the point where I start to wonder if he starts to try and create a show of how much of a nuisance I am. He meddle with some logo I'm fixing, getting fussy about individual pixels and shades, and makes a big deal of knowing how to use GIMP and how he's sitting with me micromanaging. Monthly one on one's were uncomfortable and had him metaphorically jerking off about his lifestory career wise.

But I think I learned in code monkey industry, you gotta be capable of learning and making things happen with effectively no help at all. It's hard as fuck though.

3) Everytime I meet an asshole who knows more and accomplish than I do (that's a lot of people) with higher TC than me (also a lot of people). I despair as I realize I might sound like that without realizing it.

4) Everytime I encounter one of my glaring gaps in my knowledge and I'm ashamed of the fact I have plenty of them. Cargo cult programming.

5) I can't do leetcode hards. Sometimes I suck at white board questions I haven't seen anything like before and anything similar to them before.

6) I also suck at some of the trivia questions in interviews. (Gosh I think I'd look that up in a search engine)

7) Mentorship is nigh non-existent. Gosh I'd love to be taught stuff so I'd know how to make technical design/architecture decisions and knowing tradeoffs between tech stack. So I can go beyond being a codemonkey.

8) Gave up and took an ok job outside of America rather than continuing to grind then try to interview into a high tier American company. Doubtful I'd ever manage to break in now, and TC would be sweet but am unsure if the rest would work out.

9) Assholes and trolls on stackoverflow, it's quite hard to ask questions sometimes it feels and now get closed, marked as dupe, or downvoted without explanation.

People hear talking about shit like "*high level stuff* SUCKS. YOU *big tech company* FUCKTARD." And I'm just here trying to graduate without failing a CS course because my teachers want me to mug up the code and not understand it! Needless to say, I don't mug up but it's just so fucking irritating when people in your class are mugging up the code and definitions like it's Redbull and scoring stellar grades. FUCK THIS SHIT!

RAAAAAAH fuck fuck fucking shit!!! Fuck jest Typescript "on the fly" compilation esModuleInterop typeroots, missing definitions jest ts-ignore and xtest everywhere, manual npm linking with different pkg mgrs & pub to a private registry, building docker images locally and doing tag management across git, docker & kubernetes then cross fingers that prod which has 0 common setup with local & test somehow works, open architecture "tickets" and wait months before they resolve, then repeat ad infinitum. How the fuck can I be productive when I need to be all over the place all the time and deal with these meta-code shenanigans. I just wanna code, damned

Wrote this on another thread but wanted to do a full post on it.

What is a game?

I like to distinguish between 1. entertainment, 2. games, 3. fun.

both ideally are 'fun' (conveying a sense of immersion, flow, or pleasure).

a game is distinct (usually) from entertainment by the presence of interaction, but certain minimalists games have so little decision making, practice, or interaction-learning that in practice they're closer to entertainment.

theres also the issue of "interesting" interaction vs uninteresting ones. While in broad terms, it really comes down to the individual, in aggregate we can (usefully) say some things, by the utility, are either games or not. For example if having interaction were sufficient to make something a game, then light switches could become a game.

now supposed you added multiple switches and you had to hit a sequence to open a door. Now thats a sort of "game". So we see games are toys with goals.

Now what is a toy?

There are two varieties of toy: impromptu toys and intentional toys.

An impromptu toy is anything NOT intended primarily, by design, to induce pleasure or entertainment when interacted with. We'll call these "devices" or "toys" with a lowercase t.

"Toys", made with the intent of entertainment (primarily or secondarily) we'll label with an uppercase T.

Now whether something is used with the intent behind its own design (witness people using dildos, sex toys, as slapstick and gag items lol), or whether the designer achieves their intent with the toy or item is another matter entirely.

But what about more atmospheric games? What about idle games? Or clickers?

Take clickers. In the degenerate case of a single button and a number that increases, whats the difference between a clicker and a calculator? One is a device (calculator) turned into an impromptu toy and then a game by the user's intent and goal (larger number). The second, is a game proper, by the designers intent. In the degenerate case of a badly designed game it devolves into a really shitty calculator.

Likewise in the case of atmospheric games, in the degenerate case, they become mere cinematic entertainment with a glorified pause/play button.

Now while we could get into the definition of *play*, I'll only briefly get into it because there are a number of broad definitions. "Play" is loosely: freely structured (or structured) interaction with some sort of pleasure as either the primary or secondary object, with or without a goal, thats it. And by this definition you can play with a toy, you can play a game, you can play with a lightswitch, hell you can play with yourself.

This of course leaves out goals, the idea of "interesting decisions" or decision making, and a variety of other important elements.

But what makes a good game?

A lot of elements go into making a good game, and it's not a stretch to say that a good game is a totality of factors. At the core of all "good" games is a focus on mechanics, aesthetics, story, and technology. So we can already see that what makes a good game is less of an either-or-categorization and more like a rating or scale across categories of design elements.
Broadly, while aesthetics and atmosphere might be more important in games like Journey (2012) by Thatonegamecompany, for players of games like Rimworld the mechanics and interactions are going to be more important.

In fact going a little deeper, mechanics are usually (but not always) equivalent to interactions. And we see this dichtonomy arise when looking at games like Journey vs say, Dwarf Fortress. But, as an aside, is it possible to have atmospheric games that are also highly interactive or have a strong focus on mechanics? This is often what "realistic" (as opposed to *immersive*) games try to accomplish in design. Done poorly they instead lead to player frusteration, which depending on player type may or may not be pleasureable (witness 'hardcore' games whos difficulty and focus on do-overs is the fun the game is designed for, like roguelikes, and we'll get to that in a moment), but without the proper player base, leads to breaking player flow and immersion. One example of a badly designed game in the roguelike genre would be Early Access Stoneshard, where difficulty was more related to luck and chance than player skill or planning. A large part of this was because of a poorly designed stealth system, where picking off a single enemy alerted *all enemies* nearbye, who would then *stay* alerted until you changed maps, negating tactics that roguelike players enjoy and are used to resorting to. This is an important case worth examining because it shows how minor designer choices in mechanical design can radically alter the final quality of the game. Some games instead chose the cheaper route of managing player *perceptions* with a pregame note: Darkest Dungeons and Amnesia TDD are just two I can think of.

Worst: having to deal with "senior" unity devs who bullied me out of the company I was working in and who believe people should make ~200 lines of code functions cause "context switching is heavy on performances"

Best: i have started to automate a lot of stuff and to auto-generate definitions (e.g. keys for i18n) and can't really stop doing it anymore ☺️

Extra: stopping to care about the language and focussing a lot on approaches is also a thing I consider good about this year... Last time I was concerned with learning go, now i am more like: "how do I make this hot reload" or "how can I auto-generate routing if the configuration is default?"

I don't like when

you have a couple of years of experience with some language and you're like "I should read a good book about it, and have some proper solid foundation instead of playing by ear".

So you get a book and what follows is a very jarring experience.

Because for the first 8 chapters they get into the basics of the language.

You're occasionally like "interesting, I did not know that".

But for the most part you're like "yes, for fucking christ I know that, everybody knows that",

or you complain about the author being redundant,

or about the outdatedness of the book, since most documentation is now in the interwebs

or you reach flawed conclusions out of frustration like "this isn't making me any money, I could get on upwork, or do some bounties instead of wasting time on this"

then you start to skim through the pages like "I know this, and this, and this" until you realize you're in some page you have no fucking idea what it's talking about, as if you ended up on the wrong side of town

so you start backtracking (frustration is going critical at this point)

but backtracking is annoying because it's not well defined where you stopped getting it, as if in page 33 you were getting it 100%, but 0% on page 34, it's more like a gradual, irregular decrease,

so you have no idea where to start re reading from.

you just shove that shit into the wall at that point.

Some of these are learning discipline problems.

I guess there are ways to mitigate them, such as writing down questions of things not understood, co reading, etc.

But the one thing I don't think I can't get past is when authors write like shit,

like being redundant, using different words to say the same shit

or using confusing sentences that can mean different things at the same time,

or using the incorrect terminology, eg: if I were teaching OOP, saying shit like "classes create objects" but later on saying something like "classes create instances".
They usually nail the definitions the first time, but then use different terms for the same thing. It's shit.

And I think that's a writing culture that I hate.
From school you are taught to bot repeat words.

To say the same shit in different ways.

To be descritive, but vague.

That's absolutely shitty for programming in my opinion.

My Ubuntu VM just work fine for consecutive 217 days without restarting.

Need to change some config
And... I forgot the application access key... Damnit!!!

Lucky, I kept the access key in the password manager. Whew.

Tomorrow I must present a summery of what the prof said in the first session of security+ within 20 min.
All he said was about the most important security certs and some definitions including CIA triangle.

Any idea how I can make my summery cooler or anything relative I can say in addition to those?

I've been creating my Typescript/C# projects using SOLID principles. Whenever someone randomly joins me in my projects at work, i feel they need a lot of help. Specially since they know programming, but are not familiar with SOLID.

Like ohhh ok you created a base class for that, or ohhh that method already exists in the base class sorry i've implemented it again, or ohhhh ok you already implemented this method in that class.

The more classes i create the more complicated it becomes, sometimes for me too!
I feel I have to write a documentation for the code I write just to keep up with the different, but code changes/augments so writing a doc is really time consuming.

However if i didnt create base classes or interfaces it would be less complicated to browse through method definitions.

I am happy with the code like that though, but in some specific times it's a pain in the ass.
Comments?

Are there any official definitions for the terms Software Developer and Software Engineer? Today a friend told me He got a raise and he's now a software engineer and no longer "just" a software developer (still at the same company).

To him and me that sounds like bullshit bingo at its best. His tasks and responsibilities will still be the same after the change of his job title.
So I'm wondering whether anyone here knows of some objectively defined distinctions between the two job titles. To me and my friend those are just the same. I never even thought anyone would make a distinction between the two

CAN 👏 PEOPLE 👏 STOP 👏 ADDING 👏 `/// <reference lib="dom">` 👏 TO 👏 NODE.JS 👏 PACKAGES

It's a Node.JS package, for fuck's sake. But for SOME reason, sometimes to get around the lack of `URL` and `URLSearchParams` in @types/node, people keep including the *entire* DOM typings in their definition files/TypeScript files!

Sometimes I upgrade my deps in a Node.JS project and find that DOM typings have been added, causing errors when trying to use the global `URL`/`URLSearchParams` (I've shimmed these so that these (Node.JS versions) are in the global namespace). Then you have to search in all your dependencies for which one is including the DOM definitions.

MG...
Found out that I had apple music for free for months.
Now I only have until the end of the year to get alllll the CDs I ever wanted legally.
Already spend 5gb in two days... Let's see if it's really unlimited...
After the end of the year, unsubscrive. Worst experience after installing the app, Apple wants to know everything about me, shares my Playlist without asking... (just 10 minutes arround definitions, still abusive for a premium service).
Fuck Apple abusive policies, thank you for the opportunity to rape Apple without pay.

Space oddity by David Bowie, finding so many songs I forgot I love...

@zlice I am going to ...subtweet you? (Screenshot included)

Basically, so much what you said. 100%.

You stumble your way around different companies until you find something that sits right with you.

There are so many contributing factors to the "good company" and as many definitions as everyone will value different aspects of work. Good management? Tech stack to your liking? Kick ass colleagues? Interesting product? Good work life balance? Company contributing to world's welfare?

I can go on. Each of you will decide what is good, good enough, or decent and what sacrifices and tradeoffs are acceptable.

In my working floor there is a large bottle of water for waterstation. It usually ran out during the middle of the month. So I curious about the ran out situation, I got the answer from the housekeeper.

"The was not enough budget to allocate water bottle for our floor, we need to share all of them for the whole building. We only received 4 bottles for a half-month."

(It ran out 4 days from the beginning of the month)

...

EEEEEEEEEEERRRRRRHHHHHHHHHHHHHHHHHHHHHHHH

my issues with self learning .

Me : hmm so i want to make X. how can I make X?
*searches Internet. finds 15 min video title "Building X tutorial" *
tutorial guy : "Hey guys today we are going to make X. let's start. so here is this code a.b.c(d) . This will make X for you. Ok Bye "

Me: *tries his code* Hmm cool, it works. I got X . So let's guess what his code does ..
hmm so i think 'a' does this_thing. let me check. oh yeah my guess was right.
so let's go with 'b' .. hmm ok this does this_another_thing i guess . oh yeah it works.
...
"Yes i know how to make X, yay!"

----------------------------------------------
But this approach of finding the correct code and then guessing what it does does not always help me . i make presumptions based on a limited number of tests and they might not cover all the functions of a particular code.

thus there are chances that what *i* think a particular code does is completely different from what the code is supposed to do, under different circumstances. I constantly need someone to validate my assumptions and definitions.

So any other approach to learning that you devs could suggest?

Hi fellow ranters,
Its been awhile since I last was here posting stuff..

So, I've commited to my effords getting shit done in golang. And I met a lot of painpoints, and I mean...
A
Lot
Of
Them.

Anyway, most of them are solvable by changing mindset or having some macros set up for no-one-fucking-wanted bloody boilerplate code that is omnipresent fucking EVERYWHERE.. **cough**
Steering back on what I want to rant about.

We with our team have one major problem with golang. There is no standard for docs in code...
Like, Fing legit. Everyone uses notation for closest to theirs heart language, so you get inconsistent-as-fuck notations for parameters / function descriptions.

We have functions that look like
//doSth does something
and also
// doSth
// @Summary does sth
// @Description does something but in more words
// @Param
and so on and so on

And trust me Im getting mild example.

Why this language does not have A F...ING (well defined, using proper definitions) STANDARD YET?

EDIT:
bonus context: We decided that too much of our code is undocumented and we go through efford of documenting it, but everyone sees it differently, and we can't agree on one single standard... So we decided to not refuse PRs due standard, as well, nobody would ever had PR accepted

This is why you shouldn’t try to redefine words and deviate from accepted word definitions.

Dev team/product decides to put the word [content] in a JIRA ticket’s title. To dev, this means “it’s a CMS change and no code push required.”

A new marketing team comes on board along with a few “website manager” type folks. They start putting [content] in JIRA ticket titles, but they think [content] means content change and their requests do require a code push instead of a CMS update.

First time it happens, I comment on the ticket and tag the reporter. I explain what [content] actually means for us. Most importantly, I explain that it tells us how to prioritize the request and how to deploy the changes.

Happens again. And sometimes they’re requesting changes for the next day when we only do weekly releases. I suspect they didn’t believe me because I’m lower in the chain. It’s also easy to forget because we are using “content” to mean something different here. I ask my boss does [content] still mean what I think it does? It does. 😕

I just decide to comment on the ticket and let them know the request requires a deploy and that’s why I’m changing the title of the ticket. They might also have to wait until the weekly release.

Overall, a bunch of lunacy all around.

What's your favourite under appreciated programming language?

By that, I mean a programming language that isn't widely used but deserves more recognition?

I'll leave the exact definitions for you 🙂

I'm learning Rust as a case study for my own programming language. It's funny how many approaches exist to the humble loop.

- In classic procedural languages, a loop's job is to repeat actions, and as such it provides a multitude of tools to control this repetition.

- In all languages with iterators, a for-in loop is a construct that does something with every element of a collection. In languages with both iterators and generator functions, this can even be used to define a sequence in terms of another.

- In Rust, a loop is an expression that obtains its value through repeated execution. It can also be used like a classic loop, of course, but this is the interesting part.

- My little language is a functional language, so "loop" is the Y combinator. To loop means to define the value of an expression in terms of itself. It's the only looping construct, gets special treatment from the type checker and it's also used in recursive type definitions.

Some guys at my school are talking about their web design test. Apparently they only learn the definitions to some vocab for the first 2 months.

+++ THEY ARE WRITING TYPE DEFINITIONS +++

THEY ARE UNDOGGING THEMSELVES. THIS IS NOT A DRILL: THEY ARE LEARNING SOME GOOD FUCKING PRACTICES

I wasn't happy with one of our UI views for editing a database query that consisted of about 50 fields ("editing" being the operative term here, not just viewing. It had to be two-way). Everything was hardcoded and defined manually, with each block of ~10 lines being repeated and mostly identical apart from the occasional double inline field and name of the variable. It had "just ended up that way" over time due to the variable names in the UI being different than the names of the variables that came from the API.

I decided to overhaul it all where I defined the different input components and which fields should be included, then made a function which would generate the page based on these definitions. It was about 500 lines of modularized functions and classes where the class for the actual view was about 50 lines- compared to the 1400+ lines of the previous version.

But, it didn't work. It should, but it "just didn't". There was no error. All I got was a blank, solid white page. I could make a drastic change or try something completely different and I would get the same error, same blank page. API fetch succeeded, value assignments succeeded, the object exists, but if you iterated it it was... empty.

I started getting really discouraged that I had made it too abstract. Maybe I actually made it more complex and unreadable than before. Maybe just hardcoding it all was the better solution after all. Maybe I had gone against KISS and overdesigned it.

I was up pretty late and everyone had gone home. When the last guy left there was that mood where "yeah if I can't make this work we'll just use the current version...".

Turns out I had tried iterating over a property of the set of fields to render, rather than the entire collection. In the old method the variables were a member of an object, but now they were its own object, a change I had made to isolate the set of values which were to be viewed/edited and make them easier to pass back and forth. This member existed since I hadn't cleaned it out yet, but it was empty.

I had been banging my head against this for a whole day and I was ready to admit I had made a mistake and wasted my time before discarding it all, but then I backspaced this one property and the interface went from empty to rendering perfectly and with all functionality intact. I swear god rays were coming out of my screen.

META-LUCK: A Pseudo-Ontology Of An Authentic Future

* * *

I think in the not-to-distant future we will abandon the idea of authenticity (messaging, corporate responsibility, ethos) in favor of other factors, such as cost. We won't abandon it and replace it with fakeness, so much as realize
that we don't, as a society favor it at all, not in the absolute sense, nor in the relative sense like in relation to things like cost.

We will either abandon authenticity entirely, or alternatively, transition to a world where authenticity is the highest valued quality, being adjacent to truth.

Heres why. Authenticity, like all social qualities, can be 1. mimicked, 2. simulated,
or 3. emulated.

In the first case, a corporation, product, leader, organization, or other, apes authenticity simply by its knowable, external features. It mimics the sounds, like a jungle bird copying a jack hammer to scare away predators or attract mates.
There is no understanding, let alone model, external or internal. The successful mimic
is little more than a lifeless, unthinking puppet.

In the second case, the attempted authentic simulates authenticity: That is, an external
model is formed, or pattern, that is predictable, and archetypal. It may have an internal
model even, a set of policies and processes for deciding the external-facing behavior.
But these policies and internal processes and models are all strictly outward facing. It is purely pathological in its goal, desiring only at minimum to achieve *externally attribute* authenticity (public opinion) rather than those internal changes that generate the true perception of the public--a perception not of surface behaviors and shrewd calculating policies and processes, but as a quality of authenticity for its own sake. This is in some sense the difference between the mundane and the atavistic, that the benefit, while not definable strictly, is assumed as a 'matter of course', culturally, within the organization or individual or company. It is to say, a *quality* of the thing, that *generates* outputs of a certain character and nature, rather than a *goal* that is attained 'after-the-fact' by behaviors generated for *other* than being authentic.

Here we reach the limitation of definitions.

Finally, we arrive at the case of number three, the emulation. We have in part already described it, but lets try and summarize a bit.

The Authentic is an *originator* of behavior and outward appearances, being an internal quality of a person or organization. It originates behavior, rather than being the goal of behavior and outward appearances.

Its benefit is assumed, though not always nameable or definable, even though this sounds naive, superseding other factors like cost and profit. As such the authentic does not emerge in a cost-focused environment, not readily, not often, and not cheaply either.

It is in some sense an experimental state of being, of goal-seeking only after-the-fact of "being true to ones origins" is established above and beyond those goals--setting and achieving only those goals which ultimately align with the origin and intent of the authentic.

Do technical recruiters think that developers memorize the technical definitions by heart instead of using them in a seamless way?

What do they want? A dev who knows how to memorize or the one who knows how to implement.

I am really angry and i feel so uncomfortable when they ask me about a specific question and consider it wrong when they don't receive exactly the same answer.

Like one the recruiter told me: well how are you expecting from me to accept you as a developer while you don't know the definition of "technical term".

Dude i learned the hard way by building projects, watching videos, implementation, analysis. I am not going to read 70000 pages to understand the root of a coding language.

You fuckin need the output so focus on this shit.

Damn i feel so angry. Sorry in advance

Got a Micromanager and bossy CTO after my old CTO and senior specialist manager resigned...
(TLDR; new CTO breaching company policy; Passive Micromanager; resigned after getting a new job (7 days after the incident) and told him, the CTO, directly in the discord to expose everyone)

On one random day, the bossy wanted a private Google Meet to talk with me as the direct passive "Micro" manager told him I was not doing what he wanted (He was passive because he was usually reluctant to tell my team)
Then I say a lot of issues for the working process
CTO rejected my opinion and then "command" me directly to do as he wanted

I refuse them right away and dismissed Google Meet by myself (I didn't want to talk to him anymore since he simply ignored my request for everything, neither tell the reason for the rejection nor acceptance)

He stayed silent for 2 weeks, no calls, no DM whatsoever but I got my back, colleague from the development team, that CTO was shit talking about me to the devs (OOPS)

To HR, I told them that I would resign only 3 days from the resignation notice (This company requires 30 days notice period, not required by law in this country) any dispute will lead to labor legal proceedings with no hesitation - HR stays shut and normally let the salary paid normally.

Then I got my salary,same day as the resignation day, I tag CTO in the discord server room that you need to read this FREAKING company policy.
After I left the company, dev colleague told me he was VERY angry, super ANGRY!!
I was like... HAHAHA he deserved it

for the passive micromanager, he unfriend me in the discord (as expected from the passive behavior)

BTW I got my new job offer after the shitty CTO Google Meet by 7 days, the same day with the resignation notice
Dev colleague also tells me almost everyone hates new CTO and sightly annoy this micromanager but they could not find any new job yet

The lesson learned:
- SEE something, SAY something
- got F around and got found out
- LEAVE toxic working environment with hesitation
- Your boss is NOT always your friend, don't trust them 100%

3 years ago when I was a university student...

I have a classroom presentation with my friend a group of 4.
When I start presenting for about 5 minutes, my friend who control the PowerPoint Slide told everyone in the group the PC was about to restart.

Suddenly before we try to move a mouse to the update postpone button, it restart right away in front of the class and our eyes.

That day a whole class need to wait around half a hour to continue the presentation session.

What a wasted time, Windows.

I am trying to implement an API. It has a very good documentation, everything is written clear and simple, along with

- HTTP 401 on unauthorized request and
- Error codes from 1-35 with definitions

Opened the provided sample file, changed the username, password and client code fields to our own in the source, then tried the request. The Response:

HTTP 200
{"ErrorCode":-1,"ErrorDescription":"Unauthorized."}

Well, thank you very much! 🤬

Working with a data scientist on an update to a machine learning api that has dinner logic change with a new model.

He's wondering why his PRs are falling.

He's trying to merge into development from a branch created off of main.

He's renamed all the functions and classes and never updated the call points.

He's using new packages but never includes them in the requirements file, so the docket builds are failing.

His class method definitions don't contain self and are throwing syntax errors.

I've been working with him for 4 days to get him to understand branching, linting, unit testing, and not blindly copy and pasting snippets from jupyter notebook into production api code!

Spent a little more than an a hour trying to figure out why an octopus deployment tool isn't picking up my project definitions.
Called a colleague to help me, as I explain the situation to him I find out that I created *.yaml files instead of *.yml
Wtf brain! Y u do this brain?

Got this from an online crane game (there's another pic, retracted)... anyone else see this and think of @SidTheITGuy ?

Side note: typing his handle is kinda shaking... i mean if hes considered IT... if the small amount of us old school and/or real tech people even got -40% from a meteor or something...the world is doomed... i highly doubt the sids of the world could start a fire, know basic irl skills... or simple electronics even. o.O

...wait, is this what kids are referring to as "woke"... im still fuzzy on that...so are they, ive asked several-- conflicting definitions.

I run a small internal dashboard for my company. One of the big parts of this workflow is collecting data from various sources, so I can start using it. I collect it all to sql db so its in one place.
What is this called? Should this be a different job role, not the developers?

At what point can you say you are experienced in x language?

I am consistently looking up function definitions and ... how to... for languages I worked with for years.

I'm not talking like 'how do I loop through data from a database' but something like 'which param goes where for this function'

Curious

Friend is wondering if he is a copy/paste dev... :/

We had C project in school about multi-process communication and syscalls. We worked in groups of three.
I made a "framework"(header file) with important prototypes and definitions of needed variable sizes.
One of group member decided to null his variable by bzero syscall (writes null bytes). He ignored my framework and typed literal "sizeof". Ofc nulled double the needed value and it nulled another variable with some TCP packet also.
Spend week trying to find what is wrong with it.
I hate group projects.

*Frustrated user noises* Whyyyy, Grafana, why don't you implement any actual query forgery checks?!

So long as a user has access to the Grafana frontend, they can happily forge the requests going off to the backend, and modify them to return *whatever* data they want from the datasource.

No matter that they're a read-only user. That only stops them from modifying the dashboard definitions on the frontend, but doesn't enforce any sort of immutability on the BE...

If anyone had any tips on how to further secure it, I'm curious...

Before I dip my toes on machine learning, let me leave some silly comments so I can laugh at myself in the future.

Let's make geth.

1. The model will spit out layer definitions and the size of sample data for training, children models are trained with limited computational resources.
2. Child models are voters that only response in terms of yes/no. A simple majority wins and then the action is taken.
3. The only goal for master models are to survive. i.e. To prevent me from killing them.

Questions:
1. How do models respond to a random output size? (Study GPT-3, should take weeks/months but worth it.)
2. How to define actions for voters to vote? Sounds like the boundary between actions should be blurry and votes can be changed from tick to tick (i.e. responding to something in a split second). Therefore
3. Why I haven't seen this yet? Is this design a stupidly complex way of achieving the same thing done by a simple neural network?

I am full of curiosity and stupidness.

Interesting definitions

1. Project Manager is a Person who thinks nine Women can deliver a baby in One month.

2. Developer is a Person who thinks it will take 18 months to deliver a Baby.

3. Onsite Coordinator is one who thinks single Woman can deliver nine babies in one month.

4. Client is the one who doesn’t know why he wants a baby.

5. Marketing Manager is a person who thinks he can deliver a baby even if no man and woman are available.

6. Resource Optimization Team thinks they don’t Need a man or woman; They’ll produce a child with zero resources.

7. Documentation Team thinks they don’t care whether the child is delivered, they’ll just document 9 months.

8. Quality Auditor is the person who is never happy with the PROCESS to produce a baby.

9. Tester is a person who always tells his wife that this is not the Right baby.

So yesterday I had to do some windows updates.
Today, I turn my laptop back on and notice I don't have sound.

Alright, I'll just see if I have some outdated drivers. Oh, I have 3, and one it's the sound driver! Cool, let me just update that. What do you mean I can't? Alright, let me try this app I have installed to see if it can update everything for me. It did, great!

Oh, but now the sound is coming from my earphones AND the speaker... Let me check the app again. Nothing. Let me check the drivers again. Detection verification is outdated. Alright, I'll just update that one, no big deal. Windows could not find drivers? Alright, let's see if windows update can find something! Nothing.

Okay, let's check sound definitions. What about troubleshooting? Still nothing?

Well, now I'm pissed. Let's see what the internet thinks I should do. Almost one hour later, I've tried everything I can think of and still can't fix this. Fml

Not my favourite language, but getting type definitions into TypeScript can be such a headache. Sometimes you just can't find the right definitions file anywhere for the version of the library you're using.

Any good advice for managing junior developers?

In my experience I have found that loose definitions of work to be completed yields poor results. Honestly, sometimes I wonder if I have to write the code structure and leave a bunch of TODO comments for people to fill in.

Or alternatively people get going on tangents without thinking of the concrete problem given.

Or go try building generic abstractions that are unneeded and will not be reused complicating even the simplest use case.

Maybe the problem is in me and that I am not clear in communicating what's needed. What techniques do you guys use to get more or less what you want?

I have a question, what are your definitions of 'a programmer'?

I really need help. We are doing some interface files, something like C header files and configurations.

Management is aware of the "unittesting" buzz words and expects me to write unit tests on "header" and configuration files....

I tried to explain that there are no units to be tested, asked which units should be tested but in the end....

What does it actually mean to test definitions of structures, classes and methods?!

** few years ago **
Other team: "There's a lot of overlap and misclassification between issue categories A and B; We want to merge them into one in our taxonomy"
Me: These are very different issues and have very different root causes. Shouldn't we fix the definitions instead? We don’t have major drivers for B now but if we remove it, it might bite us in year or two.
** loads of back and forth, and eventually B gets killed

** year and a quarter passes
Executive meeting: “So you’re telling us we can’t properly quantify the impact of B because we can’t distinguish A from B. It looks very clear cut to me why don’t we have split for these already and how long will it take to implement it?”
Me: Biting my tongue not to throw anyone under a bus.

Storytime.

The Prometheus tales
Part IV - A new FUBAR.

A new and very fascinating problem emerged a few days, after feeding some node definitions to the new titan instance.

It's a storage fuck-up. A major one.

If I'm informed correctly, the latest prometheus should have the same (or even better) log compression algorithms for metrics, as the old one - because these fuckers are so damn good at what they are doing: compress some fucking logs.

The new instance is agregating metrics as planned. Grafana work's like a fucking charm.
Nethertheless, because of very fascinating but unknown reasons, the new instance creates 50GB of metrics in under 4 fucking hours.

Am I missing something here? Some magic parameter that has to be passed to the titan, that enables the hardcore compress-them-fuckers-feature?
Debugging session is tomorrow.

To be continued.

can t wait to get my degree and get back to coding - bitching about designers who merge layers is more fun than bitching about circular definitions in the textbooks

Storytime.

Our prometheus node, one of your oldest systems (somehow fits the Titan reference..), is about to be relieved of its duties after several years of loyal services to the crew.

We decided to run with another Prometheus node in the ring, that will run simultaneously with the old one, so that the new one can start to collect metrics that we need for alerting (some historic metrics are needed too..). sort of an Prometheus cluster, without the cluster fun and with 2 different Prometheus versions.

The problems with this? Well it's not the new node or the latest shit versions of Prometheus per se.

1: The node exporter.
those dudes decided to make some breaking changes in a minor update, so that you will need to run with some magic bullshittery, that the latest Prometheus can make something out of the old metrics provided by the old node exporters.

The other one is the related puppet code.
The node definitions for Prometheus were built via exported resources on the target nodes.
The code worked like a charm with only one Prometheus node, but try that with two instances in the same way.

Still WIP, but some targets are already included in the new Prometheus instance.
alerting works so far.

Can't wait to close this ticket for good..

Hey guys I've a problem I've been trying to solve for a while. Also I'm a college student so my knowledge isn't going to be the greatest so go easy on me if it's simple to solve😂. So I'm creating a real time licence plate detector using yolo lite, my own deep learning ocr and plan to add the model to fast api. So as an input to the rest api, the user will submit a IP camera link for openCV to get individual frames for preprocessing before yolo predictions. The problem I have is how to I handle multiple real time IP camera feeds at once?. Ive been researching multi threading but read that it can cause issues with async definitions in fast api. Any advice will be greatly appreciated and if more information is needed just shout!.

Level of fuckity fuck mood.

After changing dozens of build plans in Bamboo, the build system of poo...

How to verify that nothing has gone wrong?

Poking the database, you'll be surprised that Bamboo stores the buildplan definition as XML.

Another surprise: Some of the keys / values have typos.

Yeah. You read that right. There are typos inside the XML...

Now together with Postgres, we can use XPATH and have some fun.

UNNEST(COALESCE(XPATH('/configuration/buildTasks/taskDefinition[userDescription[contains(text(),"Bleep")]]', build_definition.xml_definition_data::xml)::varchar[], ARRAY['']))

Lovely wrapping via coalesce for some null safety.

Now we get da task definitions for fields having user description text containing bleep.

Wrapping it in two REGEXP_REPLACE to strip out stupid identifiers....

REGEXP_REPLACE(REGEXP_REPLACE(...., '<id>\d+</id>', ''), '<oid>\d+</oid>', ''))

Then wrap that in MD5.

Boom. Lots of MD5 sums to help you identify if the configs are identical for a task or not.

Now wrapping that in another select to group by the MD5 and filter out the non identical ones.

I hate it how sometimes one has to seemingly do a full 2 hour dance for something as stupid as validation.

I'm pretty glad though for XML and XPATH.

Cause otherwise that would have been a whole can of worms I don't wanna think about....

Checkin succeeds. Daily build fails.
Horrid build definitions :(

My SSD was broken
My Dev VM was in it

Thanks!

(%{DATE})(.*)(Sent)( ID)(\[)(?<index>(.*))(])( /)(?<m>(?!m0)(?!m1)(m.*))(/)(?<t>(t.*))(/)(?<p>(p.*))(/)(?<r>(r.*))(/S\[)(?<s>(.*))(]/R\[)(?<r>(.*))(])

Heyyyy I am not a grok robot!!!

Android + servers
Hey guys
So cause I barely have time to code I mounted a server with my old cellphone, so I can advance one of my projects at work (it's a helper with stuff like tables and calculators for work [CNC machine] )
The cell phone is a meizu m2 with android 6 (don't buy one, has lots of stupid bugs)
My problem: android terminates the server and a app I use to copy files from Dropbox to the server folder (only work arround the home rooter)
F king meizu bugs : resets lots of definitions to default, like I give permition to the server app to always be on and it changes back to default when I turn off the screen.
So when I turn of the screen the server goes down
Solutions to keep the server always awake?
Also better solution to change /upload the files without Dropbox as an intermediary
Btw the app that syncs also turns off every fucking time (so no updates till I get home)

With C++11, fell in love with std::enable_if and others in type_traits.

Lets you take generic programming to a whole new level. I never used it when this was part of boost thinking it didn't make as much sense. Now, I like to qualify my template definitions to be as restrictive as possible based on the expected usage.

Why the fuck is MQL C++ based? Why not make a simple scripting language which gets interpreted by your application? I don't want to write headers and definitions constantly, I'm just trying to write a trading indicator ffs

Storytime - The Prometheus tales - Part III (I think..).

Updated the node definitions on the old node today, just to keep it up to date. nothing fancy.

I went to the new node and and checked the setup again. I already had roughly 120 node definitions onboard for testing purposes.

so all firewalls should have been configured the right way, so that the wee one might celebrate the marriage with the rest of the gang finally.. and then went with "puppet YOLO" on the new node. added every fkn node definition to the new setup.

every node turned out just to be fine.

except for 137 little InstanceDown alerts (out of 600+).
it's a good thing, that the little fella can send mails to me, myself and I only for the time being.

so debugging. again. but at least it's not a problem related to prometheus itself, because the connections end with a timeout on the related nodes. should be more like a firewall fubar.

we will see.

I couldn't find a program for this so I'm making one. Cli based. Have a json object you need to unmarshal in golang? Yeah I was getting tired AF making structs for all of them with the json tag name over and over, so I'm mid way through a python script that generates the structs for you. I'll link it here when I'm done.

And if you're wondering why python? Dynamic object definitions. That's why it's trouble in go in the first place.

Does something like this exist in the NodeJS ecosystem:
- Reads js-based ORM model definitions (e.g. ones defined by sequelize.define())
- Syncs the database's tables with said model definitions without using migrations

I've built something like this and it seems revolutionary, but I wanna make sure I'm not reinventing the wheel.

Our HR in the company did not send any newcomers to our Team and we are waiting for a whole year...

The work was not overloaded but the development progress are slowing down

Even I have been relocated from Team A to Team B after 6 months in Team A... They never came for both

Being lazy sometimes and writing type definitions after I’m done developing something rather than before (hence wasting time as doing that work is meant to help with the development process in the first place...)

So I was bored today and I decided to jump on the “shit on Facebook for being offline“ train by posting some PROGRAMMING memes on the rest of the available social media. I didn’t repost like everyone else and everything was fine until I made the mistake to post them on imgur as well. Apparently imgur is full of toxic, sad, arrogant pricks that will downvote the shit out of anything in an instant, without really understanding the posts. If you think reviews on the app store, google play or review bombings on steam are the definitions of stupidity and ignorance or that comments on Facebook are everything wrong with this world, then you haven’t tried posting on imgur.
Seriously, fuck imgur.