Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I just noticed programmers can cite Shakespeare in 1 character.
"To be or not to be..." = 2b|!2b = true = 17 -
"Programming language is a convention to give order to computer. It is not supposed to be obscure, bizarre and full of subtlz traps. These are the characteristics of magic" - Dave Small9
-
Not exactly dev stuff, but LaTeX low-key makes me nervous.
In writing my thesis it seems that through some keyboard-fuckery I managed to slip in some weird unicode bullshit character somewhere, so that it doesn't compile. Alright, I just do \DeclareUnicodeCharacter{0301}{ASDF} so that it gets replaced by ASDF. Searching for ASDF in the output pdf file does not yield results, so I can't even find the location of the fuckery in the text. It seems that unicode character is somewhere in my .bib-file and I guess my citation style doesn't even render the part of the data that character is in after all. So the above hack works, but still there is some weird-ass character in my bibliography file that I can't find.
On another note: I get that modularity is cool and all, but who thought that it is a good idea to give people zero transparency over what macro stems from which included package? No namespaces etc. I end up including a whole lot of packages that are needed for exactly one macro. That bloats up the file and you have no way to trace back which macro came from which of the quazillion included packages.
...then again maybe I'm just a lazy piece of shit whose google searches end before success and all of the above has some easy fix.9 -
Random citation by p100sch (https://devrant.com/users/p100sch)
today while playing Minecraft:
"That moment when your family tree software throws recursion errors..."3 -
Oh dear people,
Congrats for going nuts @-red -style!
You have hit the cap! @Cup0coffee!
At first I thought I didn't know what to say, but here have a modified citation:
"Friendship is _C_are.
Do you know what I'm saying to you?
Friendship is rare." [2001 - by guess who]
7 -
I'm in a Cafe and listening to two people, who I'm pretty sure are recruiters, generalizing so hard on what it takes to get a job. It's taking every inch of me to not shout, CITATION NEEDED3
-
"Programming is a craft. At its simplest, it comes down to getting a
computer to do what you want it to do (or what your user wants it to do). As a programmer, you are part listener, part advisor, part interpreter, and part dictator. You try to capture elusive requirements and find a way of expressing them so that a mere machine can do them justice. You try to document your work so that others can understand it, and you try to
engineer your work so that others can build on it. What's more, you try to do all this against the relentless ticking of the project clock. You work small miracles every day.
It's a difficult job. "
- The pragmatic programmer -
markdown is not good enough! the tools aren't there for non-devs and there's no concordance on moving forward *compatibly* for anything other than headers and __possibly__ lists.
md has been around for years and still no consensus on comments, meta data, css, data imports, etc.
i could never in good faith recommend to a non-dev to use markdown, even though every academic and professional writer from legal to journalism should exclusively be using markdown to write and store their documents. the data portability and ease of search, retrieval, collection, distribution, etc of markdown compared to pdf or docx is enormous. markdown is the hex format of text, the perfect layer of data and visual so that the user and the computer can both operate on text as blocks of data rather than weirdly styled paragraphs that need to be reformatted BY HAND for citation-style or journal format, or paper size. FOR EACH SUBMISSION. Academics literally rewrite their 100-page papers to accommodate up to 10 different submission requirements.
They could be clicking MLA vs Chicago and/or using a journal's stylesheet to recompile for its styles.
Today there is some support from zotero et al to take away some of the pain, but it makes ZERO SENSE for writers to have to keep and store and keep up to date, multiple versions of the same document. Git pull does not exist for them. But the worst part is that git isnt the solution to their problem. They need a compiler more than they need version control. But they also desperately need vcs. They ALL literally have a million files named "dumdum.dumFINAL-3084_lastversion \2020, this one.dum".
They dont have git or anything like it, because they need a line-by-line solution like markdown for git to become effective.
All of writing is basically mired in the fact that people cant even roll up their paragraphs and see what the fuck it is theyre saying. Most writing reads like a long scroll through some nonsense that goes nowhere. Like this rant. but the point is that markdown and line-by line editing actually produces more logically sound writing. You start to think in terms of defining ideas in blocks, ... like code.9 -
age++;
Normally, I'd leave it there like most other people. But this is devRant, not Facebook [citation needed], so let me take the opportunity to talk about a dev-related project I'm mulling over.
A number of years ago, I dropped my music hobby in exchange for focusing on my computer science/programming skills. I'm now at a point where I'm working professionally as a developer, and I've wanted to get back into music for quite some time. Specifically, I want to make music, not just perform it.
Thing is, I've had difficulty trying to find a good platform for uploading WIPs to get feedback from. I'm hesitant to post them on social media platforms for a variety of reasons (though I'm open to budge), so I've been considering alternatives.
So here's my idea: A personal blog made from the ground up that details my journey rediscovering music, including tracking the resources I've used for others to refer to, music samples, etc. I think it would be a great opportunity to not only get feedback on music I've made, but to also incorporate my programming skills with my music hobby.
I'd appreciate any feedback on the idea, as well as any advice/recommended tools for taking on a project like this.4 -
!rant
Teller (of Penn & Teller) once said that magic is sometimes just spending more time on something than any normal person thinks is reasonable
Found online, need citation...
Top Tags
Weekly Rant
View