- Sleep 7h+ each night (you think you don't need it - but you do!)
- drink NO coffee (you've slept enough!)
- pair-up (you're not as good as you think)
- get a grasp on the problem (it's time will spent!)
- communicate constantly (you're not alonw especially)
- refactor just as much
- learn from you partner
- celebrate even small accomplishments (you need success!)
- go home and do something else (your pet project does not need more than 5hrs per week!)
- repeat (because repetition makes perfection!)

Algorithm: from the Greek "algos" (pain) and rhythmos (repetition), we derive the true meaning of this word: REPEATED PAIN.

:D

Me: "DRY (Don't Repeat Yourself) is a good mentality."
Other devs @ company: "I'm so wet rn."

This story starts over two years ago... I think I'm doomed to repeat myself till the end of time...

Feb 2014
[I'm thrust into the world of Microsoft Exchange and get to learn PowerShell]

Me: I've been looking at email growth and at this rate you're gonna run out of disk space by August 2014. You really must put in quotas and provide some form of single-instance archiving.
Management: When we upgrade to the next version we'll allocate more disk, just balance the databases so that they don't overload in the meantime.

[I write custom scripts to estimate mailbox size patterns and move mailboxes around to avoid uneven growth]

Nov 2014
Me: We really need to start migration to avoid storage issues. Will the new version have Quotas and have we sorted out our retention issues?
Management: We can't implement quotas, it's too political and the vendor we had is on the nose right now so we can't make a decision about archiving. You can start the migration now though, right?
Me: Of course.

May 2015
Me: At this rate, you're going to run out of space again by January 2016.
Management: That's alright, we should be on track to upgrade to the next version by November so that won't be an issue 'cos we'll just give it more disk then.

[As time passes, I improve the custom script I use to keep everything balanced]

Nov 2015
Me: We will run out of space around Christmas if nothing is done.
Management: How much space do you need?
Me: The question is not how much space... it's when do you want the existing storage to last?
Management: October 2016... we'll have the new build by July and start migration soon after.
Me: In that case, you need this many hundreds of TB
Storage: It's a stretch but yes, we can accommodate that.

[I don't trust their estimate so I tell them it will last till November with the added storage but it will actually last till February... I don't want to have this come up during Xmas again. Meanwhile my script is made even more self-sufficient and I'm proud of the balance I can achieve across databases.]

Oct 2016 (last week)
Me: I note there is no build and the migration is unlikely since it is already October. Please be advised that we will run out of space by February 2017.
Management: How much space do you need?
Me: Like last time, how long do you want it to last?
Management: We should have a build by July 2017... so, August 2017!
Me: OK, in that case we need hundreds more TB.
Storage: This is the last time. There's no more storage after August... you already take more than a PB.
Management: It's OK, the build will be here by July 2017 and we should have the political issues sorted.

Sigh... No doubt I'll be having this conversation again in July next year.

On the up-shot, I've decided to rewrite my script to make it even more efficient because I've learnt a lot since the script's inception over two years ago... it is soooo close to being fully automated and one of these days I will see the database growth graphs produce a single perfect line showing a balance in both size and growth. I live for that Nirvana.

That feeling everytime you realize that you could have built something better with less code and repetition after completing a project.

Ok, so when I inherit a Wordpress site I've really stopped expecting anything sane. Examples: evidence that the Wordpress "developer" (that term is used in the loosest sense possible) has thought about his/her code or even evidence that they're not complete idiots who wish to make my life hell going forwards.

Have a look at the screen shot below - this is from the theme footer, so loaded on every page. The screenshot only shows a small part of the file. IT LITERALLY HAS 3696 lines.

Firstly, lets excuse the frankly eye watering if statement to check for the post ID. That made me face palm myself immediately.

The insanity comes for the thousands of lines of JQuery code, duplicated to hell and back that changes the color of various dividers - that are scattered throughout the site.

To make things thousands of times worse, they are ALL HANDED CODED.

Even if JavaScript was the only way I could format these particular elements I certainly wouldn't duplicate the same code for every element. After copy and pasting that JQuery a couple of times and normal developer would think one word, pretty quickly - repetition.

When a good developer notes repetition ways to abstract crap away is the first thought that comes to mind.

Hell, when I was first learning to code god knows how long ago I always used functions to avoid repetition.

In this case, with a few seconds though this "developer" could have created a single JQuery handler and use data attributes within the HTML. Hell, as bad as that is, it's better than the monstrosity I'm looking at now.

I'm aware Wordpress is associated with bad developers due to it's low barrier to entry, but this site is something else.

The scary thing is that I know the agency that produced this. They are very large, use Wordpress exclusively and have some stupidly huge clients that would be know nationally.

Wordpress truly does attract some of the most awful "developers" and deserves it's reputation.

If you're a good developer and use Wordpress I feel sorry for you, as you're in small numbers from my experience.

Rant over, have vented a bit and feel better. Thanks Devrant.

Let me paint you a picture.

It's the day after code freeze. Code has been branched. It's time once again to verify tickets and run smoke check so we can begin our 3 days of blitz testing before we deploy.

As a team we all have roles to play in this process. Yet, every stinking release it is like pulling teeth to get everyone to take the initiative and verify tickets and run smoke check. Our principled engineer even reached his limit this morning and blew up on everyone.

When you are being paid good money to do a job, you need be an adult, be responsible, step up and do your job!

This feature I'm building requires crossing over to a second application for some actions (fair, this reduces repetition), but the method used for it is kind of ridiculous.

To keep with the existing patterns, I followed suit, and added two PATCH and a DELETE routes, wrappers, and calls. (Typical CRUD + de/reactivate).

But. This freaking halfassed HTTP model doesn't support anything but POST and PUT! wtf. (Also, the various IDs, naming schemes, and required json data/formats differ across view, controller, and endpoints. but whatever?)

Two and a half hours later, and the feature is done and works wonderfully. Four times the functionality of the previous incarnation, and the code is only about 25% longer! haha.

Ahh, I'm complimenting myself again. (but somebody has to, right? 😅)

but really, when i want to get something done i'm actually surprised at how quickly it all comes together. Even when I need to patch API Guy's madness.

(and this time I actually found someone else's code in the mess! It was actually worse!)

I suppose taking a day off yesterday did me some good.

codeCertain - Duolingo styled code learning platform that emphasizes learning by repetition. Be certain of your code.

Php code without any class. Every page is a separate php file in project root folder.

Everything is all over the place, code repetition is everywhere.

The worst part? No security. The sql calls are with mysql_ functions and string concatenation. Files are just uploaded without checking.

And I had to repair it.

So like a year ago I decided that I was gonna learn programming. And the thing that popped into my head was HTML and CSS. So I browsed some websites where you could learn some HTML and stuff. But I never really got into it and eventually stopped and moved on. Now I just kind of got a sudden urge again to learn programming and build a website again. So I started browsing some sites and found a suitable one. Since I'd already kinda learned the basics it was all kind of just repetition. And now I've got a very basic site set up with Apache that I was thinking I'm gonna use as my homepage. And I also got my very first experience not understanding what the fuck is wrong and browsing stack overflow for an eternity. Turns out it was a simple missing semicolon. Welcome me to the dev world!

probably the one who sent me 3 mails within 10 minutes regarding 3 different positions, and all were addressed to someone else (Hello, Mr. Completely Different Name), so i replied telling him that's not me, and gave him the info to fix it in their db. he apologized profusely and said he fixed the error.

Next day I got two mails for another two positions, with the same incorrect name.

Or the one with whom I had half an hour phone "interview" for a specific position, they couldn't answer even the most basic technical question about the project, but invited me to an in-person interview and said my questions will be answered there, the phone interview was just to make sure they don't send completely offtopic people to the interview with the client (so far acceptable).

On the in-person interview, it was partially a repetition of the phone one, but okay, lady from the company is talking to me first time in her life. We get to the part where I can ask my questions, so I ask those basics about the project again, and her answer is:
"Oh, i don't know, i'm not a technical person, you'd have to ask that to the technical person from the company, I'm an hr person from the recruiting company."

"Wait... so... not only was this whole meeting a waste of my time, but you also lied about what it is, when you scheduled it with me on the end of the phone interview?"

"Well... it wasn't a waste of time, we like to meet the candidates in person before we forward them to actual interviews in the company, to make sure that they're not completely offtopic."

"... and how exactly do you think you'd be able to evaluate that, since you're not at all a technical person and know nothing about the project??"

" Well, i talk to programmers a lot, so i've picked up quite a bit of the terms."

...

So the incompetence of this knob-head are unbelievable, so in our company there's a particular method that required to return object specific way like
{
'a' : 'b',
{
'c' : 'd',
'e' : 0,
}
};
}

which somehow will be use everywhere in the project, I decided to create a constant class therefore anyone can use it and prevent redundant code. (re write the same thing over and over again). He decided to tell me to rewrite the same method for every-time I needed to return data.

My method is to avoid writing the same thing in repetition , that is why I place a method in a constant class where I call every-time I need to return those data in the specific way.

But he prefer writing it in repetition. OMG

Music. Music teaches you numbers, creativity, patterns, structure, and basically primes your brain for math and creativity in that space. In addition, it teaches you how to think both within a structure and outside the box, as well as the importance of repetition, memorization, and learning a new language.

Music really was my second language, and the ability to read/write it fluently is a skill that takes a long time to master. I really believe that it increases your brain plasticity so much.

!rant

I figured out a way to make your code readable!

The main idea: make everything into a function. Each function should be small and you should gradually use past functions to build future functions.

Depending on the language and the size of your code you should make your functions with different sizes, but always keep them small.

This function splitting allows for debugging small parts of your code, avoids repetition and abstracts your code, each making it more readable.

What is it about SQL that invites people to do things in utterly ridiculous ways? The amount of pointless repetition and complete lack of clarity in the query scripts I get handed is irritating at the best of times - without any documentation (or even a bare comment sometimes) how am I supposed to work out what you were doing?

Here's something not quite a rant, but relatable. And an issue. For me at least.

------

You get really proficient with a set of tools.
- Can solve things in an efficient & elegant manor.
But it's now boring.

You find some new exciting stack, research like a madman. Possessed.
Your perfectionist self, seldom doesn't want to settle.
You burn out from pressure & deadlines.
You feel inadequate, imposter syndrome settles in.

You reminisce of the easy days when you (thought) knew everything.

Decide to rebuild using that past stack.

Gets bored.

You notice something new & exciting.. loop iterates to next repetition.

devRant needs some sort of Offspring-of-Clippy tool.

"It looks like you're posting a sort-of-humorous-the-first-time joke or meme. Have you bothered to scroll more than twice to see if this dead horse has, indeed, been well flogged?" 😜

rant="""
It's too many features for me to keep up with. And the client just bounces between this matrix of all the possible permutations of them, refusing to admit that he is asking for mutually exclusive behavior in more than one place. I have mentioned to him at least 12 times a year that there is too much going on, not organized, we need to simplify, prioritize, or we will have 100 half baked untested features.

Of course it is more or less made it out to be that this is all my fault, or at least it's hard not to feel that way when I say:

It will be a long time before X will be working, we need 25 other things first.;

Next day he asks:
Have you made any progress on X;

I reply: Now we need 24 things to be done at this rate it will be a month.;

He replies:
Ok but I need this yesterday. How about if you add a new feature Y that does everything X does without those 24 things?;

I reply: That will not work at all like X. Y is just X + 1 more feature.

He replies: Ok well I need Y so when you're done with X I need a way to do it like Y also. I just thought it'd be easier.

EASIER TO ADD MORE FUCKING FEATURES YEAH SURE THATS EASY AS FUCK YOU FUCK FUCK FUCK. He's a nice enough guy, pretty smart compared to my first few paying gigs, but wtf really? How do I come out and tell you I need 25 days and you ADD more work? This was one example.

IN TWO days he has added 12 features. And during the week has asked for 29 UI interfaces to be COMPLETELY different. This is becoming COMMONPLACE. Every week there is either a huge change, or a conversation like about that finds its way into the entire business flow inside an dout.

The worst thing is: I TOTALLY understand what he needs. I feel that HE doesn't. This weekend I spent literally HALF of his retainer on getting equipment into my hands to bring it back to find out it DOESNT WORK. Why aisn't HE doing this so I can finish the features from NOVEMBER that HE NEEDS in order to PROCESS SALES.

I've tried and tried but I just can't get through to this client what a tremendous waste of time his \"process\" is, for lack of a better word. Constant changes, contsant additions, lack of clarity, needless repetition and contradictions, constantly adding moonshot ideas to compete with every industry in the region, and not beta testing anything until something goes wrong.

Fuck this guy! His business is failing and I felt responsible for the longest time but it is clear to me that if I wanted to save his business I would have to ignore 95% of his feature requests. I ignore 50% now because of the stress in trying to determine which of the 3 different paradigms he is talking about changing. I will lose this client, and I feel like he will sue me to get all of his money back. He holds me to very little honestly - BUT WEEKLY reminds me that he won't be able to pay me next month if feature XY and Z arent ready!

If a developer is CLEARLY overwhelmed, it makes NO sense at all to continue to PILE ON feature after feature
"""
try:
while true:
rant+=", after feature"
except DevHeadExplodes as inevitable:
raise YourDevsRatesOrLookElsewhere(inevitable)

So in the project I’m working on we were about to do a push to live, no major functionality just minor adjustments and nice to have stuff. One of the things I did was a reminder, nothing special just sends an email out if something hasn’t been done for 3 days and then sends an email every day following. Push to live and every thing goes fine with no issues. Day 1 there are no issues. Day 2 there are no issues. Day 3 and I’m inundated with people telling me that the emails are getting sent to practically everyone, shit. What have I done? What have I missed?
So I start looking at the live database hoping for a data problem, no such luck. I look at my code looking for something blatantly obvious but nothing. I start replicating the data but I can’t reproduce this bug and it’s annoying the hell out of me. I checked one of the emails that the client sent to us more thoroughly and seen that it was sent at 07:01. This is odd as our webjob runs at 1am so I start looking at environmental factors and started looking at release management, more out of hope than expectation. I check the staging environment and see that the webjob ran at 7:00. Coincidence I thought, the webjob gets packaged on the release pipeline and everything in the database was dummy data anyway but I’d better check anyway. The database was an exact copy of the live database, turns out a “senior developer” wanted to sanity check everything by running live data through the code so he copied the database over. It was fine for the first couple of days but the data was now 3 days out of date triggering my email code and I get hit with the shit storm. I’ve never met such an incompetent developer in my fucking life, functions 700 lines long, classes that are over 20000 lines, repetition every where and the only design patterns he’s used is when he picks up a child’s colouring book. I can live with the fact that he writes code like someone on their first day of University But copying a database because he wants to “visualise” the fucking data is absolutely farcical. No wonder the project is fucked with a “developer” (in the loosest possible use of the word) is at the helm.

I get it. Hooks prevent code repetition. But personally I hate them. I don’t know why. I just don’t like writing them. Maybe it’s because I like writing “this”. Weird, right?

I'm a C++/Obj-C programmer finding it ludicrously hard to switch to Swift.

I find that the constant ability (leading to very poor programmer code) to reduce syntax and add tokens reduces readability and nowhere is this more apparent that with closures.

I'm working through (to my shame) Ray Wenderlich's Swift course and the closure chapter has this:

PS I loathe K&R as much as I do Swift so it's all in Allman formatting for clarity.

let multiply: (Int, Int) -> Int =
{
(a: Int, b: Int) -> Int in

// do Something else

return a * b
}
Why oh why isn't this more simply and elegantly written as:

let multiply = (a: Int, b: Int) -> Int
{
// do Something else

return a * b
}
The equals sign shows clearly that it's a closure definition assignment, as does the starting 'let'. But this way all of the stupid excesses, like the 'in' keyword, the repetition of the params / return type only this time with useful labels and additional tokens are removed and it looks and reads much more like a regular function and certainly a lot more clearly.

Now I know that with the stupid ability of Swift you can reduce all this down to return $0 * $1, but the point I'm making is that a) that's not as clear and more importantly b) if this closure does something more than just one line of code, then all that complicated stuff - hinted to by the comment '// do Something else' means you can't reduce it to stupid tokens.

So, when you have a clousure that has a lot of stuff going on and you can't reduce it to stupid minimalism, then why isn't is formatted and syntactically better like the suggestion above?

I've mentioned this on the Swift.org (and got banned for criticising Swift) but the suggestions they came up with were 'use type inference' to remove the first set of params / return type and token.

But that still means the param list and return type are NOT on the same line as the declaration and you still need the stupid 'in' keyword!

Idk why but I can't stand GIFs. Their constant repetition translates into noise and becomes unbearable.

Few days back, I developed an app for a client where users can buy textile designs online.
The designs to be uploaded on the server must be square to display correctly on the app. so I had to make them square manually (by either pattern repetition or by filling extra space).

I was like "fuck me!", 800 design image to make it square and each takes like 1 and half minute. I did uploaded 30 to 40 images and then...

I got really frustrated and I was lazy to make more designs square anymore.. So I developed an algorithm that would identify the type of design and then it automatically makes it square by self decision.

so that was my little anti-laziness for my big laziness.

I'm so sick of "senior/lead" developers pretending they know how to write tests and ending up with these unmaintainable test suites, full of repetitions and incomprehensible assertions.

You should take some time to learn from your mistakes instead of just continuing to write the same shitty tests as usual!!!

Every time I arrive at a new team I spend weeks just trying to understand the test suites for what should be fairly SIMPLE applications!

UNIT TESTS SHOULD TEST UNITS OF CODE!
If your unit test tests seem to be repetitive, they are not unit tests. Repetition is expected in integration tests, but that is why those are usually DATA DRIVEN tests!!!

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.

The overwhelming annoyance when you figure out that the thing that's been causing your code issues for the past 3 hours....
Is because you did a greater than comparison rather than a great than or equal to...

“A person who thinks all the time has nothing to think about except thoughts. So, he loses touch with reality and lives in a world of illusions. By thoughts I mean specifically “chatter in the skull”... perpetual and compulsive repetition of words... of reckoning and calculating.

I’m not saying thinking is bad. Like everything else, it’s useful in moderation. A good servant, but a bad master - and all so called civilized peoples have increasingly become crazy and self-destructive. Through excessive thinking, they have lost touch with reality.”

Right now, everything. I started at a Consulting firm because I expected many new problems to tackle, solutions to develop and generally to always have a fire burning underneath my ass but instead I always develop the same standard bullshit.

I miss the days in my old job when there was just a problem and the task to solve it. When I stared down giant amounts of data, just KNOWING that somewhere in that mess is some structure I could exploit and that short moment of inspiration when I finally pinpointed it. The rush of endorphins when the solution became clear and everything fell into place to form a beautiful pattern amidst the chaos test data, git commits and numpy arrays.

Now its just "Yeah, would you just write another selenium testsuite that throws out fail or pass and wastes all the information because the only reason I'm a testmanager is because I'm too incompetent to do anything else and not my passion for the field".

The constant, mind numbing repetition of always the same patterns where the occasional dynamic element that becomes stale is the highlight of my work week... I would have never thought that making good money with easy work would ever get me as close to depression as it did.

Having three places with identical, easily separatable code, would you call that code repetition?

The age-old question between `DD/MM/YYYY` or `MM/DD/YYYY`.

After some shower thoughts, my new preference is `YYYY/MM/DD` for Americans and Lithuanians (only 2 that I know) it just looks like the year has been placed first, otherwise, they read it as normal. To everyone else, the date is reversed and therefore will be read in reverse leading to the same answer.

In addition, `YYYY/MM/DD/some-dated-file` as a file path works exceptionally well for storing files as it uses the least amount of repetition.

Recruiters on LinkedIn will be like: "I just came across your profile and ...". Scrolls up the message history and there is the same message a few times with a different job.

I know recruiters have to send out tons of emails and using templates makes it a lot easier, but at least make and effort to make it look like you aren't just reusing the same message over and over.

There is so much confusion in the world of programming right now, at least for me. I bet there’s only so many concepts going on and that these concepts are realized in certain ways. E.g. programming following certain paradigms and practices, also different workflows, containerization, agile, devops etc.

When searching for tutorials in different subjects it’s horribly aggravating to learn to use the tools. Not because they are inherently hard or bad in any way. There’s just so many different tutorials, some badly given, some that are great but which bring up to many foundations you already know so you find yourself getting bored to the point that you just stop listening. Many tools are used for so many use cases, sometimes overlapping each other, they use concepts to that you’ve heard hundreds of times before. Many times they want to do things in a special way so even if the concepts are the same you still need to fucking listen to the same old thing while learning how to write a command a slightly different way or how some tool is supposedly better than another.

I’m realizing that what I’m so sick of is the lack of TLDR information about new tools with some short description of how to use. Where you didn’t have to re-hear stuff you already knew or had heard so many times unless for a very good purpose, such as to show exactly how it’s done differently than another relevant tool. In a dream world the TLDR information could also remember my skills and remove the parts I didn’t need to know about any new tool.

[POLL] How do you develop stuff?
1 - just write code. It doesn't need to be organized, it just need to work how you thought it would, and THEN you start organizing things, like editing/creating new files, letting things DRY, optimizing the sutff you did earlier;
OR
2 - you surgically write code, making sure you keep everything is organized from the beginning. Basically you only write when you are sure.

Or maybe it's a blend between the two or something.

I'm asking because I do like the #1 and I feel uncomfortable when people see my code when it's under development. It's a mess, there are tons of comments everywhere and a bunch of repetition. But, when I find the right stuff, I start writing modules to make my code work better, remove unnecessary things, add documentation, and so on.

My development process is not the best of the best, but I get things done with it.

Setting up a task with windows task scheduler is fucking confusing if you need time-based repetition. At least if you're not doing it in english. Some options seem like the same thing, some are probably badly translated.

Customer pays an extra charge ($) for using a thing over time. Unlike some customers this charge isn't broken out separately anywhere is and actually it is hidden in an overall bill / number they receive that is just a non itmized sum of a bunch of stuff...

They want an accurate number.

This request came up in a meeting and it was so bonkers that it had to be repeated like 8x ;)

The repetition isn't so bad really as at least it indicates everyone was all "uh wait wut!!?!?"

The constant re-explanation of how stuff should be done, whether it's business logic or even in simple programming itself. When it comes to developers, I find myself repeating myself a lot simply because they can't be bothered to understand what business rules are needed as all they want to do is just code a solution and get it over and done with.

On arriving in the corpse of a once proud city I was less than astounded as I walked out the station to see everyone I’d seen before
Literally everyone
There they were in walking denial of almost a decade or more in some cases
Sitting having the same prepared conversations
Driving by blasting music
Walking their I dog
Shoplifting the same goods

And their repetition as usual causes wildlife to become confused and perform the same activities
The rats ran about
At least five of them in familiar scurrying movement
Over bold from being ignored and well fed
Filthy dirty rats
Just like the people
Filthy dirty monsters
Living like the needle in the groove
Eating away at my brain
With such violence I want to leap into an unsurvivable scenario and return back to where I just came from just to see a different brand of freak do nothing in a different fashion and throw off the routine

So.
Trash
Surrounded by it
Am not it

And it accumulates
Why is telling the truth ignored ?
Why should my life be reduced to mindless repetition while they add further temptation to simply throw said trash in the dumpster ?

Nothing seems to be enough for them
One slight after another
Wtf is wrong with them ?
Blank souless husks
That's what they are and what being around them leads to people being

But hey they're "powerful' when shredding themselves in the garbage disposal and limiting the time experiences remembered or proven to have existed

Or against things exactly 3 feet in heigt

Killing them would be a mercy
Their hollow brainless minds will learn eventually

Ok why tf are some apps that just generate random number need in app purchase? Bitch please?

You know what, I’m gonna write one, and I’m gonna make it free, tell me what features are needed, what I have in mind is: random number between, random N numbers between, random N numbers between without repetition, random from list with and without repetition, what else? Let me know.

Just bitched out the same customer service woman telling her I wish her and everyone like her would just die so I wouldn't have to waste another day recovering my own goddamn property i keep double paying for.

I'm sick of having to buy the same movies and games just so some butt sniffing pederast can have a pay check.

speaking of pederasts, table 2 just showed up. more assholes with potential copies in the same places. while two creepers i could also photograph sit behind me for some reason.

so sick of repetition.
and you fucking cunts wouldn't even need to be bothered with this if you hadnt stolen soooo much of my time without adequate recompense.

not that i'd of course agreed to this insanity.
but these people should have to suffer AND pay us.

Apparently this generations idea of ergonomics is fucking skewed to resemble video game controllers they only get good at via repetition they only get by fucking around.

Instead of a sticking to a known format to operate heavy dangerous machinery

I mean if you have to learn you'll learn but Jesus another point regarding their stupidity

Sometimes I wonder if we’re not all trained models that are self teaching and pivoting around so that some mindless clone can mimic us until they actually understand what the hell we thought and felt but more quickly

Like doing math problems but saturated in trauma and unhappiness or more trauma and unhappiness lol but the repetition is linked to more complex activity and then quickly forgotten since this isn’t life

Just being exposed to ideas that interested me as a kid made profound changes in what I talked about and how I thought

Are we sacrificing humans so subhumans can think like us in the future ?

Fucking pod people

There's no one correct way to get better. As with any skill, practice is one of the best ways to hone those skills. Various methods for that. Researching best practices, repetition, personal projects, professional development classes, online resources like codewars, codecademy, learn _ the hard way, etc

Every day has repetition in it of course but why become animatronic dummies ? Literally same shit. Stop doing the same things because I mention that you're all weird mother fuckers that do the same shit ! If that is even the case ! People used to have differing conversations unless they were borinh mudbrick stacking shit covered peasants! At least they built up different behaviors god

New word of the decade thus repeated
Do you know what the word Sisyphean boys and girls ?

That is how we best describe our efforts to unfuck people who drag us around in their ceaseless brainless repetition that literally has no point

Good day,
Please I need someone to help me with this:
I want help on a python code that'll display a 8x7 matrix such that numbers 1-9 appear without repetition in each row and column and the numbers appear at least six times in the table