Dev: Hey our current server is starting to chug a bit. Can I get approved for $1200 additional spend to double the speed?

Manager: *Sharp inhale*. We need this project to cost as little as possible, we really can’t justify spending any additional money for any reason right now.

*2 days later*

Manager: YOU ARE APPROVED FOR $100,000 TO IMMEDIATELY IMPLEMENT SOMETHING RELATED TO NFTs IN ANY OF OUR APPS. THE BUSINESS NEEDS TO EXPAND INTO THE METAVERSE ASAP IMMEDIATELY. I NEED AN ETA BY EOD AS TO WHEN THIS CAN BE ROLLED OUT.

Dev: …

(Qt + OpenGL) didn't piss me off for a whole week..
My point clouds are rendering great..
I guess I could speed it up a little bit..
I'm doing good..
So yeah..
no rant..

I need to render point clouds in OpenGL for a project I'm working on. The problem is it just becomes too damn slow when the point cloud size increases. So I'm trying to use LOD methods and nested octrees to speed things up. Also, I need to render text too in my OpenGL scene. So now I'm stuck trying to show proper labels using Qt and OpenGL which is completely pissing me off by the way. And I'm not doing the actual speeding up thing I was working on earlier on and before that I was working on the actual function of my program. So I'm now deviated from the deviation.

Fuck my brain.

Just read this in LinkedIn:

XYZ is one of our top star developers, with #speed as maybe her strongest super skill. She develops and ships new features at a rapid pace, at any time of the day (and night)…

This sounds super toxic for some reason. I’m triggered

!!rant
!!ANGER

Micromanager: "Hey, Root!

Since you're back, and still not feeling well, we have an easy ticket for you: Rewrite the slack integration gem! Oh, you don't have to re-implement all of it, just make sure it all works the same way it does now. That bitch you worked with once over a year ago who kept throwing you under the bus to management and stealing credit for your work? Yeah, she wrote the original code like four years ago. It's perfect, so don't touch it. but she can fill you in on all the details you need and get you up to speed on how to test it.

But yep! It should be simple. and I just knew you would love this ticket, so I saved it just for you. Nice and quick, too, to get you an easy win.

You know, since you have to repair your reputation with product. and management. and the execs. and the rest of the team. and me. Yeah, product doesn't trust you so they don't want to give you any tickets. They just can't trust you to get them out and have them work. So you have a lot of hard work to do."

Spoiler: The bus-thrower wasn't much help. (Surprise.)
Spoiler: The ticket was already in my backlog -- one of a grand total of two tickets.
Spoiler: I don't find the ticket fun. Maybe if I was to write the entire implementation with a nice DSL? but no, "don't touch the perfect code." Fuck you.
Spoiler: It isn't going to be nice or quick. But, she (micromanager) is looking to lose me, so that really is an easy win. for her.

And. just. argh. fuck you. i've been exhausted and dying for well over a year, but you've kept ignoring that (and still are, despite me providing goddamn legal forms from fucking doctors stating it in plain fucking english, which you also fucking ignore), and you just keep piling on the work and demanding the ridiculous of me despite it. Yeah I can pull it off sometimes. No, I really shouldn't, and I'm surprised I can. (also, "Time off? What, and lower your productivity even more? ____ doesn't even take vacations. And how are you doing on that ticket?") And no, none of my tickets have ever had any fucking problems. Not even when there are upstream service outages. Not. a. single. fucking. one. Ever. And the only things I've ever missed were things that bloody product never put in the fucking ticket, so fuck you with your "repair your reputation" bullshit.

god, i fuckiNG HATE THESESTUPOID ANWETLJAF SAJEWTKW BITCHFACEDUCKFUCKERS

Why the FUCK am I still fucking working here?
Right, because I've been burned out and dying so much I can't pass a fucking interview so I can fucking leave.

jasdkl;fk

ugh. Anyway. If you ever find yourself starting work at a Cali fintech company whose internal mascot is a very fine duck? Just run. I absolutely guarantee you will be miserable.

Biggest challenge I overcame as dev? One of many.

Avoiding a life sentence when the 'powers that be' targeted one of my libraries for the root cause of system performance issues and I didn't correct that accusation with a flame thrower.

What the accusation? What I named the library. Yep. The *name* was causing every single problem in the system.

Panorama (very, very expensive APM system at the time) identified my library in it's analysis, the calls to/from SQLServer was the bottleneck

We had one of Panorama's engineers on-site and he asked what (not the actual name) MyLibrary was and (I'll preface I did not know or involved in any of the so-called 'research') a crack team of developers+managers researched the system thoroughly and found MyLibrary was used in just about every project. I wrote the .Net 1.1 MyLibrary as a mini-ORM to simplify the execution of database code (stored procs, etc) and gracefully handle+log database exceptions (auto-logged details such as the target db, stored procedure name, parameter values, etc, everything you'd need to troubleshoot database errors). This was before Dapper and the other fancy tools used by kids these days.

By the time the news got to me, there was a team cobbled together who's only focus was to remove any/every trace of MyLibrary from the code base. Using Waterfall, they calculated it would take at least a year to remove+replace MyLibrary with the equivalent ADO.Net plumbing.

In a department wide meeting:

DeptMgr: "This day forward, no one is to use MyLibrary to access the database! It's slow, unprofessionally named, and the root cause of all the database issues."
Me: "What about MyLibrary is slow? It's excecuting standard the ADO.Net code. Only extra bit of code is the exception handling to capture the details when the exception is logged."
DeptMgr: "We've spent the last 6 weeks with the Panorama engineer and he's identified MyLibrary as the cause. Company has spent over $100,000 on this software and we have to make fact based decisions. Look at this slide ... "
<DeptMgr shows a histogram of the stacktrace, showing MyLibrary as the slowest>
Me: "You do realize that the execution time is the database call itself, not the code. In that example, the invoice call, it's the stored procedure that taking 5 seconds, not MyLibrary."
<at this point, DeptMgr is getting red-face mad>
AreaMgr: "Yes...yes...but if we stopped using MyLibrary, removing the unnecessary layers, will make the code run faster."
<typical headknodd-ers knod their heads in agreement>
Dev01: "The loading of MyLibrary takes CPU cycles away from code that supports our customers. Every CPU cycle counts."
<headknod-ding continues>
Me: "I'm really confused. Maybe I'm looking at the data wrong. On the slide where you highlighted all the bottlenecks, the histogram shows the latency is the database, I mean...it's right there, in red. Am I looking at it wrong?"
<this was meeting with 20+ other devs, mgrs, a VP, the Panorama engineer>
DeptMgr: "Yes you are! I know MyLibrary is your baby. You need to check your ego at the door and face the facts. Your MyLibrary is a failed experiment and needs to be exterminated from this system!"

Fast forward 9 months, maybe 50% of the projects updated, come across the documentation left from the Panorama. Even after the removal of MyLibrary, there was zero increases in performance. The engineer recommended DBAs start optimizing their indexes and other N+1 problems discovered. I decide to ask the developer who lead the re-write.

Me: "I see that removing MyLibrary did nothing to improve performance."
Dev: "Yes, DeptMgr was pissed. He was ready to throw the Panorama engineer out a window when he said the problems were in the database all along. Didn't you say that?"
Me: "Um, so is this re-write project dead?"
Dev: "No. Removing MyLibrary introduced all kinds of bugs. All the boilerplate ADO.Net code caused a lot of unhandled exceptions, then we had to go back and write exception handling code."
Me: "What a failure. What dipshit would think writing more code leads to less bugs?"
Dev: "I know, I know. We're so far behind schedule. We had to come up with something. I ended up writing a library to make replacing MyLibrary easier. I called it KnightRider. Like the TV show. Everyone is excited to speed up their code with KnightRider. Same method names, same exception handling. All we have to do is replace MyLibrary with KnightRider and we're done."
Me: "Won't the bottlenecks then point to KnightRider?"
Dev: "Meh, not my problem. Panorama meets primarily with the DBAs and the networking team now. I doubt we ever use Panorama to look at our C# code."

Needless to say, I was (still) pissed that they had used MyLibrary as dirty word and a scapegoat for months when they *knew* where the problems were. Pissed enough for a flamethrower? Maybe.

y'know, if your coworkers annoy the shit out of you, sometimes it's worth looking at how the company is treating them.

a lot of what i have to deal with spans from an environment that demands speed at the expense of quality and won't reward developers for their effort, cause they simply don't understand the effort it takes. we have a tiny team responsible for a nation wide program, and people are just shocked when they hear this, because the work we do is in fact amazing for a group of 5. everyone is just tired, overworked and badly recompensed for it. this shit will hit the fan pretty soon

I'm having an existential crisis with this client.

We are spending millions of $s every year to make sure the product's performance is perfect. We are testing various scenarios, fine-tuning PLABs: the environment, application, middleware, infra,... And then we provide our recommendations to the client: "To handle load of XX parallel users focusing on YY, yy and Zy APIs, use <THIS> configuration".

And what the client does?
- take our recommendations and measure the wind speed outside
- if speed is <20m/s and milk hasn't gone bad yet, add 2x more instances of API X
- otherwise add 3xX, 1xY and give more CPUs to Z
- split the setup in half and deploy in 2 completely separate load-balanced prod environments.
- <do other "tweaking">

- bomb our team with questions "why do we have slow RTs?", "why did the env crash?", "why do we have all those errors?", "why has this been overlooked in PLABs?!?"

If you're improvising despite our recommendations, wtf are we doing here???

One day I will crack. Hopefully, not sometime soon.

Speed is overrated.

internet connection "speed" in Germany might be the reason why so many people still queuing up on the roads on their way to an office despite being allowed to work from home at least in theory

A few days back I talked to a person who is far away from me with an air distance of 7937km and electronic signals moving at almost speed of light crossing countries. That was good decent conversation.

People should have mandatory lessons in vector processing.

In canteen, after lunch, there were 4 places you could place your trays. But only small, one-way corridor, for one person at a time to get there.

Every person picked the first place and while they were placing the tray, people behind them had to wait. Huge line started to form. If they, instead, always picked the last empty place, all tray places would be occupied for longer and the processing speed could increase almost 4 times.
Textbook vector processing example.

Imagine you work in a mechanic’s shop. You just got trained today on a new part install, including all the task-specific tools it takes to install it.

Some are standard tools, like a screwdriver, that most people know how to use. Others are complicated, single-purpose tools that only work to install this one part.

It takes you a couple of hours compared to other techs who learned quicker than you and can do it in 20 minutes. You go to bed that night thinking “I’ve got this. I’ll remember how this works tomorrow and I’ll be twice as fast tomorrow as I was today.”

The next morning, you wake up retaining a working, useful memory of only about 5% on how to use the specialized tools and installation of the part.

You retrain that day as a review, but your install time still suffers in comparison. You again feel confident by the end of the day that you understand and go to bed thinking you’ll at least get within 10-20 minutes of the faster techs in your install.

The next morning, you wake up retaining a working, useful memory of only 10% on how to use the specialized tools.

Repeat until you reach 100% mastery and match the other techs in speed and efficiency.

Oops! Scratch that! We are no longer using those tools or that part. We’re switching to this other thing that somehow everyone already knows or understands quickly. Start over.

This has been my entire development career. I’m so tired.

Fun fact:

The gradual speed increase in the descent pattern of the aliens in space invaders was actually a bug, due to the amount of aliens in the screen.

The more you kill, the faster they get.

A certain person here on devRant was annoyed about my phone being named “Beyond”, seeing a screenshot of my settings.

What they said: “the name, beyond, reeks pretentiousness and arrogance, you say you’re better than other people”

What really happened: during one of my manic episodes, I discovered the band named Death Grips. Their music resonated with me and helped me to cope with my derealization. In one of their songs, I misheard lyrics, and heard the word “Veyon” that was never there in the first place. Upon my inner voice pronouncing it, as it usually happens to me, a brand-new universe appeared before me, where Veyon was a name of a megacorporation that exists in a shaky spacetime plane somewhere in India. If you want to go there, three outcomes are possible: you can actually come to their building that appears to be normal, with people working inside you can talk to, and no signs of trouble in sight. Or, you can try to walk to their building, but you will never reach it. GPS will show you slowing down gradually as you get closer, but to you, it would look like you’re just walking with your regular speed, as if nothing happened. Like a function trying to reach its asymptote, you’ll never come to your destination. The third outcome is by far the most interesting one. You will reach the building, but it will be abandoned, with doors scattered on the floors randomly, some of them will disappear after you walk in, rendering you missing in this universe. Oh, and floors are guarded by robots and turrets, and they are made by Grumman, the military aviation manufacturer. Yes, Grumman, not Northrop Grumman. This building in the third outcome originates from the spacetime plane where Northrop and Grumman never merged.

The whole thing raced through my mind in a millisecond. I liked it and decided to squat the name, but it was already taken by Veyon open source software (Virtual Eye On Networks).

In some time, I bought a new phone second-hand, and named it Veyon. The next day, I took it to shower with me. It turned out that the seller lied to me about it never being fixed. It was, and in the process its water resistance was compromised. So, this phone was damaged beyond repair the next day I bought it.

The same day, I went and bought the same phone model, but brand new, and in black, as I originally wanted. I was grateful for this opportunity that helped me escape the situation where I would've been using the phone of the colour I disliked just because I cheapen out. I know myself, and I would’ve been feeling uneasy every day, hesitant to sell it and get a new one because “nothing is wrong with it, quit being this picky, it’s just a colour”, but wait, don’t I deserve to make the colour a significant enough reason to switch the phone because I care about colour, especially if it’s me who’s paying the money? Did I make this money rightfully, or am I an impostor who gets paid because of intricate lies I tell? Do I actually tell them, or do I make that up to somehow convince "them" I'm innocent? Or do I try to get attention?

I’m terrible at dealing with that kind of mess, So, I was grateful.

The only thing left to do was to name my new phone. I decided not to name it “Veyon” again, just in case. So, I named it “Beyond”, as this word is probably what the actual song said.

The monstrosity of a story above is the usual thing for me to feel. I was really hurt by you telling me the name I chose was a display of pretentiousness. Do I deserve to be pretentious? I say yes, but my voice is shaking, as flashbacks of my awful mother abusing me come in the way.

You hurt me with that comment. Let’s meet? :)

I have the feeling that the whole software industry is not making any real progress anymore. Or at least not at that speed like for 10-20 years or so. Now one company doing something somehow innovative and everybodys copying that shit and start a feature battle. Just to have more reasons to suck you into their ecosystem and grab your wallet.

“Practical” tech interviews for senior roles (from my experience): DONT worry! We won’t give you any “leetcode” problems!! Instead, we’re giving you only 40 minutes to do this huge laundry list of tasks that are simple but hella time consuming. We want to see how fast you can type. So you have 40 minutes to write a mini app while we take note of the shit ton of simple errors you make due to the time crunch as your fingers burn through the keyboard and then wonder why no one can pass our “simple” tech exam!!!!

DAMMIT!! the only tech exams I enjoy are ones that involve refactoring existing code bc everything else is a fucking speed test! I’d also MUCH RATHER take these exams WITHOUT someone there taking notes like I’m a fucking lab monkey!

wasn't a fight, really, just me having gotten frustrated after half an hour of trying to explain to a 2D animator what smear frames are, since we were making a flying hummingbird, found out that multiframe animations for the wingflaps looked like crap for its flapping speed, so i was like "oh, i know, let's just make the whole wing flap a 3frame anim, one frame wings down, one smear frame, one frame wings up, done"

cue the UNIVERSITY EDUCATED ANIMATOR looking at me with confusion, asking what are smear frames.

cue half an hour of repeated attempts at explanation, each attempt imagining him to be a younger and younger child, last 3 attempts i was actually sketching it out for him in photoshop and playing it to him (via photoshop's timeline for making animated gifs) so that he could see how it looks, which still didn't help him get it.

it turned very unpleasant towards the end, due to me getting very dumbfounded and irritated and interlacing the last couple of explanation attempts with remarks on my fascinated disbelief that a university educated and graduated animator not only had no idea what smear frames are, but isn't even getting it after having it explained multiple times as if he was an elementary school child.

at that point my boss stepped in, told me to go have a smoke, and when i came back, he managed to explain it to the animator by some of the interpersonal magic he (the boss) had.

that dude (the boss) was amazing.

p. s. the hummingbird turned out looking amazing, thanks to the smear frames.

Looks good for ₹500, eh?

What to do when you think a junior is working hard, you're generally happy with quality, but speed is way below where it needs to be?

What a joy working in a company that uses git as if it's subversion (dev branches? What are dev branches?) paired with gerrit. Getting a single, crucial change pushed to the actual repo can take days. The speed of the site can be measured in geological epochs. The interface has a charm of windows 95. Half of the builds are broken. Life is fleeting and I'm wasting it here.

Started working in big firm from past 2 months, I was learning about company, its products and what it does. To speed up things I asked one senior who has 8 yrs of exp, she said she also has no clue how things work here......
Now I know why I was hired as an urgent requirement......

How I approach the project: got an idea run at super speed thinks something important on my way there and return with the same speed. 🤔🤔🤔😐

I dont know how to timeline projects. I tell clients that it will be ready in one month. But the project will be so big that it takes lot of time to actually code it and do all the procedures around it. I m just giving them timeline based on the speed of my mind.

i had an epiphany today, in a discussion with the software architect of our new project.

i'm having the epic job to design & implement a prototype for a C++ library in a new software project and collected some inspiration in our "old" software, where i'm maintaining the module that fulfills the same functionality (i thought). i've been maintaining this module for around a year now. i analyzed the different features and stuff to consider and created a partial model of the new library.

when i showed it to the architect today, he was like "oh my god, no no no, you don't need all this functionality, this shall not be part of the new library!"

this was the moment when i realized how deeply fucked up the code base of the old module is.

imagine it like this:
you want to automate the process of making yourself a good ol' cup of coffee.
the reasonable thing would be to have

- a smart water boiler where you set parameters water temperature and amount of water to be fetched from the water supply
- a smart coffee bean grinder where you can set type of beans, amount of beans and grinding fineness
- a component where water and ground coffee are joined to brew the coffee, where parameters like duration, pressure etc. are set
- a milk tank where amount of milk, desired temperature and duration / speed of foaming can be set
- a sugar dispenser where amount of applied sugar can be set
- optionally, additional modules with spices, syrup, ice cubes, whatever for your very personal coffee experience

on requesting a coffee, you would then configure and orchestrate all components to your wishes to make you a fine cup of coffee. you can also add routines like "makeCappucchino()", "makeEspresso()", or whatever.

our software is not like this.
it is like this:
- a smart water boiler consisting of submodules that know how to cook water for e.g. "cappucchino with sugar" or for "espresso without sugar, but with milk and ice cubes"
- 5 smart bean grinders that know how to grind beans for e.g. cappucchino, espresso, latte macchiato and for 73ml of water preheated to 82°C
- a very smart sugar dispenser that knows how to add sugar to 95, 98 and 100°C coffee and to coffee made of BOTH coffee arabica AND coffee robusta beans.

etc. etc., i think you're getting the gist.

when i realized this, it was like, right in front of my eyes, this terrible pattern emerged like a foul, corrupted caleidoscope of chaos, through the whole code base of this module.
i've already known how rotten from the core this code base is, but today i've actually identified a really bad pattern that i hadn't realized before. the whole architecture is so bloated that it is hard to have an overview of the whole thing. and it would require a LOT of refactoring to repair this pattern.
but i guess it would also be infinitely satisfying because i could probably reduce the code base for 30% or something...

but unfortunately, this is never going to happen, because screw refactoring.

it's a great feeling to start this new library from scratch, tho...

is it so hard to screen capture only the relevant details necessary to reproduce a bug? i just watched a video where for 2:30 min, literally nothing happened. and half of rest of the time, they randomly click stuff, as if they've forgotten what they want to show. nobody can give me this lost lifetime back. and the testuff video player is so crappy that i can't even reasonably jump forward / backward or increase playing speed. i even prefer crappy, wiggly upright phone videos if they are on point and don't steal my time. SHOW ME THE BUG ALREADY

When it comes to using XCode, I can’t be the only one who thinks it’s a stupidly large file. Took a whole day to download, I know having a WiFi speed of 20Mb/s isn’t great but on a brand new iMac with nothing else installed you’d except it to download and install pretty quickly.

Also what is it with the Mac and things not wanting to be full screen??

5 minutes before the meeting, I get refreshed and start setting everything up. All in a sonic speed rush. Always feels like a movie! :D

Anybody else have trouble with getting stuck on very little things? Keeps happening to me in class and sometimes gets to me. I'll be able to finish most of my work in quick time and all is good (I get excited that everything runs so I'll write with some speed), but then some very very little bug is there and I get stuck on it for a very long time and I just feel bad about myself. I guess this does happen, what do you guys do to blow off some steam? I know I should just take my time since I'm still a beginner and I'll try to work on that.

The l33t h4ck3r experience: making a js bookmark that adjusts the video speed on an online LMS that reeally doesn't want you to watch at the same speed that you process information.

The trick is to continuously change the playback rate faster than the site can change it back to painfully slow.

Any backend devs here working with TypeScript? What are the best framework choices right now? I've been looking at Nest.js, but there seems to be a steep learning curve that might hamper onboarding of my (literally fresh graduate) new hires. There's also Ts.ED, which seems like the fat has been trimmed from it.
I know people will recommend something like, just using express / koa / hapi but I don't think we have the time to work with something super lightweight 😬😬😬. And besides, opinionated frameworks will speed things up for now (we have a lot of crap we want to do this incoming 2022)

How do you speed up a windows 11 laptop?

Instead of having binaries/assemblies included in every project, they should be installed on the development system and server once, as part of a new project setup, and during development as more are needed, and then, instead of having to upload all this shit which takes forever even on a high speed connection, they are just referenced by the project at runtime when needed because they've already been installed on the system.

Using LSP for a while now, of course, being also a NeoVim user, particularly attached to Vim's coding approach, I can't help but notice Microsoft's Language Server Protocol to be A LOT like Emac's editor approach to writing code. Was Emacs right all along? More so, have we actually slowed down software advancement by distancing ourselves from LISP-like languages, putting speed above ergonomics and marginalizing many would-be contributors that have more LISP-like thinking? I wonder a lot about the future of writing code and the importance of, at least pseudo, artificial intelligence in that future. As we all know how easy it is to write pseudo-ai code in LISP-like languages, have we also delayed artificial intelligence by distancing ourselves from LISP-like languages? But more importantly, IS IT TOO LATE? I mean, should we, instead of try "forcefully evolving" JavaScript, instead devise nem ways of coding with it that makes it more Scheme-like? This is a rent, but also a heart breaking moment for me, a devotee of languages like Rust, I can't stop, but wonder if my preferred language's perceived advances aren't only an actual coming back of LISP. Finally: it's heartbreaking to me that I just can't have a small sized Emacs distribution with Vim-like capabilities. Being actually able to kind of talk to your editor like emacs users could be a BIG improvement on developer's declining mental health stats.

ps: I'm not a natively English speaking person, please forgive tipos and other pedantic writing mistakes.

On another example of regressing for advancemente, the interested reader should read about performance differences and justification for it between grep and perl's regex implementation.

My current assignment is to refactor a React app and get it up to speed. All dependencies have been updated and necessary changes made. Currently I’m working to get class components moved to functional components when React hooks can replace the lifecycle methods used. Additionally I am updating it with ESLint to follow the Google JavaScript Style Guide because the code quality is questionable. What are some of the things you’d do to refactor a React application?

When I tuned angry birds with spotify and made the speed the beat of the song.

App didn't work out but who cares. Had so much f*cking fun building it.

Way to go ruin a collaboration. I wanted to have fun some making a game with one of my friends, but turns out being friends doesn't correlate to making a good team. Some of you probably know this, but I've never had such an experience, not even to almost strangers

Some tips on how to kill off any motivation to work with you:
* Casually insult other peoples ideas
* Don't consider other people's point of view
* Try to talk people out of prototyping/experimenting with their OWN ideas on their OWN time
* Completely undermine their skill even though you have no basis to go on
* Never worked with this person before
* less experienced
* don't have to give estimates on a daily basis
* don't consider the fact that there are libraries that can be used to speed up things)
* Victimize yourself, because someone is "forcing you" to become the bad guy

I don't know if that person is on here and I don't care if they happen to read this. I tried to treat you with the most respect, but if you don't do the same then just fuck off.

Anyways, there goes the idea of a "no stress, no problems" game dev project, because I wanted to see if isometric view would work better than top down.

My idea to have another person to work on a project with, to keep the motivation up backfired a by lot.

Someone within european timezones up for some hobby game dev?

i thought whiteboarding turning into leetcode mediums or harder correctly in 20 minutes or less was bad

now codesignal is fucking us over, tried my first one without researching any of the code score shit

anybody have tips for gaming the system there? i heard claims that speed trumps correctness for their point system (e.g. faster but not passing for all test cases may score higher than slower but all test cases pass) additionally code cleanliness/readability isn't weighed as heavily as the other factors

and to do problems individually to completion further rather than spreading yourself out across multiple problems in an exam

wont deny im still a salty scrub at the end of the day

I'm trying to get a non-programmer up to speed with some basic Python programming.

Any recommendations for online courses?

I'd prefer something free and text-based if possible, but any good recommendations are welcome.

I've looked at stuff like CodeAcademy, but most of the courses are behind a paywall.