Tbh neither can I.

I finally took the step.

The entire <functional> header is where it's at.

Perhaps one of the most important things I will ever learn in life is how powerful regularity is. Read up on a topic once? Understand nothing? Read more random shit on it. Keep reading. And then stare in awe as things fall into place.

I'm writing this out not because people don't know this. Almost everyone knows this. But it's nice to be reminded of it. It's nice to be reminded that learning new things and honing bew skills is never easy. It's nice to be reminded that there's great knowledge and skills waiting to be learned.

This is not meant as motivation so much as it is meant as a reminder. Our colleagues may be garbage. Our clients may be garbage. Our bosses, the interns, the new dev, and almost certainly ourselves, are almost always garbage.

But if you've learned 1-2 new things today, the day wasn't garbage.

I'm just learning move semantics...

Just started learning gnuplot yesterday. Sure, it's not the shiniest of tools, but I'd heard enough about its performance to give it a go.

It's like learning vim. You Google thrice to write a single functional line. You spend hours trying to find a single command for a single task.

But. GODDAMN. This thing's the fastest plotting framework I've ever dealt with. I love Matplotlib, but as great as its plots are, when I need to plot shit up in half a second, I've found a new friend.

Also, tutorial suggestions appreciated.

Sure, you hate Win10 forced updates. But have you tried a fresh install of Arch.

Just subscribed to this. My first subscription or even purchase, from the store. That should tell the developers something about their work. Well done.

Prof: So yeah this is going to be difficult. We're going to make the scalable math library. Then we have to make a functional finite elements library using that. Then make a multiphysics engine using that library. This could easily take your entire PhD. Are you prepared for that?

Me: May I show you something?

Prof: Sure, sure.

Me, showing him: We can use moose to code in the multiphysics. It's built atop libmesh for the finite elements. Which can be built with a petsc backend. Which we can run on GPUs and CPUs, up to 200k cores. All of this has been done for us. This project will, at worst, take a couple months.

Prof: ...

Guys, libraries. Fucking. Libraries. Holy fucking shit.

Looking for suggestions on how y'all motivate yourself past the 'No one will use this, no need to code it' phase. In a bit of a meh outlook these days.

Edit: This is mostly for personal projects.

Just got my first paycheck. Felt amazing tbh. Proceeded to make a little Python project to help me with high precision budgeting and budget analysis. So, any grad students here who invest and/or save half of their paycheck and use their own code to help them do it?

The superhuman feeling of going back to your code after a week and it all makes perfect sense, the variable names are intuitive, the doc strings are comprehensive, and the general codebase structure is sensible.

Has anyone used the meson build system for CPP? It's so beautiful. Finally, something to help us not kill ourselves during compilation.

git push --force

Actual production code:
while(1):
//A few lines of code here with a conditional break.
while(1):
//More code.

Have you ever just had nested infinite loops...

Literally every single professional breakthrough I've had is because of being better at coding than my peers. Internship, and potentially even my PhD. Granted, scientists have low standards for code...

"Well GPU main memory is L2. CPU main memory is L3. Which is why GPUs are so much faster." - cs major in my college.

Someone please confirm if this is a common opinion.

Person who has an attention span of 3 minutes, has never done math before, and has no background in any form of code whatsoever, and will never need it:"I'm thinking about learning Python."

Me:"Go for it but it will be difficult to remain motivated."

Person:"But I really want to do this."

Me:"So did every corpse on Everest."

Taking book/resource recommendations for learning CPP. Give me whatever. Literally. Whatever.

Being a programmer in a scientific discipline can be infuriating.

using "no one" ="almost no one"
using everyone = "almost everyone"

1. No one knows what even the very idea of good practice is. And everyone refuses to learn. 3k lines of repetitive copy pasted main. 500 lines of plotting method.

2. Raw C-style pointer based array creation. Won't use develope array libraries because what if development stops. FUCKING HAVE YOU SEEN YOUR CODE WHAT IF DEVELOPMENT ON YOUR CODE STOPS. FUCK.

3. LOOP VARIABLES DECLARED AT THE BEGINNING OF THE METHOD WHY.

4. Everyone wants to make modular, independent code. No one wants to use OOP. NOPE. ALL IN ONE FILE. WRITE C++ LIKE A FUCKING PYTHON NOTEBOOK. FUCK.

5. LIBRARIES OH MY GOD PLEASE DO NOT CODE UP YOUR MATRIX MULTIPLICATION. PLEASE DO NOT TRIPLE LOOP IT. NO. THE LINEAR ALGEBRA LIBRARY WILL STAY IN DEVELOPMENT.

6. Please realize that literally not one comment over an 1800 line file does not help anyone.

FUCKING. WHY. WHY ARE WE SCIENTISTS SO GOOD AT SCIENCE AND SO FUCKING SHIT AT THE CODE THAT MAKES OUR SCIENCE HAPPEN. WHY. FUCKING. WHY. FUCK.

A few days ago, I had a trashed laptop, lost my wallet with University ID and my debit card, a thesis and a poster not started, and no real content to put on either. I'd need money to get a new univ ID but no debit card. Same ges for buying a laptop. Also homework and shit due. Which required a load of Python.

Fast forward a week.

Laptop on its way, thank PayPal. Got new univ ID. Library loans out laptops. All homeworks done. Even got the replacement fee on my debit card waived by being nice to the customer service person.

I'd like to thank devRant for keeping me sane. And I'd like to say I'm fairly proud of my adulting abilities. They're not stellar, but they're pretty okay.

How many people here consider their profession a large, potentially principal part of their identity as people? How important is it to you that you are known for what you do?

I'm on a 17 hour security monitor shift. Sup devRant.

Just found some of Andrei Alexander's I'd videos on YouTube. Specifically the cppcon 15 talks. Does anyone else here know of talks or books etc all that can satisfy my near-juvenile love for fast code.

Wrote a bunch of Python scripts that alter an lsf script for software that we use in our lab. So now we have a Python 'library' of sorts that runs the simulation files, changes variables in the files, exports data, analyzes, tabulates, and continues until done.

I've automated potentially weeks of work to happen in minutes. I know this is run of the mill here, but I am fairly proud.

I fucked up on my grad school essay by sending them the PDF of my college-specific paragraphs. All of them, yes.

To correct said fuckup, I attached the actual essay, but with a college-specific paragraph meant for another school.

However, I imagine that they saw the wrong essay and then went to the paragraph list and saw the paragraph meant for them?

I MADE TWO DIFFERENT FUCKUPS THAT CANCELLED EACH OTHER OUT AND I GOT ACCEPTED.

????? PROFIT??????

Insider tips and tricks for a PhD, if we have grad students of any sort here. Literally anything at all. I'm enthusiastic but not naively so (I like to think), so let's learn stuff from the vets.

Does anyone have any recommendations for command line parsers for Python? I've looked at argparse click docopt so far. I am clearly bad at making informed decisions.

Anyone here use clojure and/or Scheme? If yes, any tips/tricks/resources?

An open source technical graphing and analysis software using Matplotlib numpy and Scipy backends.

Just landed that devRant puts a source bar at the bottom of pictures downloaded from posts here. With both devRant and the poster being credited. You guys are amazing.