\documentclass{article}
\usepackage{soul}
\begin{document}
I'm19 and I know how to use \LaTeX, \LaTeX is more used in academia, they taught me \LaTeX in Uni, but a lot of other people just won't ever heard of it because is rare to find in other places, most technical degrees and even a lot of uni ones won'tuse it \st{even if it's vastly superior to word}.
\huge \LaTeX rules
\end{document}
Latex is no versioning tool but a textsetting language. It outputs perfectly formatted Documents after building and takes care of aranging images, quotes and all the tedious stuff so after setting up your template you only have to care about content. It works well with git.
Not like word where adding an image fucks the whole formatting.
I’m a softwaredev too, we use this for our manual. Its writen in markdown, which we convert with pandoc to latex. We can use git for versioning and merging and the manuals always look very nice.
As a software developer, LaTeX makes writing documents feel elegant in the way good code is elegant. No more manually going back and saying things like “as shown in diagram 4” and updating the number when the number of diagrams changes; LaTeX can do that for you by referencing the object. Citations and bibliography are an absolute breeze to generate. It can generate various kinds of plots and diagrams themselves for you, making it much easier when you then need to make changes to it later.
With the right packages (think: code libraries) you can do all sorts of things. I like the acrodef and ac commands which lets you specify a bunch of acronyms, and then the first time you use them in a document it automatically expands it to the full version, but uses the acronym on all subsequent uses. When writing code snippets, you can have it automatically apply the correct syntax highlighting for the language you specify; though this is admittedly a feature many markdown implementations also have.
Well in this thread people were saying you can set up your own local git repository? What’s a newbie friendly way of doing that. I’ve watched videos and understand that git version control system but I can’t quite seem to grasp more than that.
I learned latex by doing my engineering homework in it. I quit using latex because I kept doing my engineering homework in it and it turns out it sucks to do
What’s a good way to learn about Latex and Git. I’ve tried learning on my own but it’s very overwhelming.
Overleaf is easy to use and has tutorials for LaTeX
Never heard of latex but I can help you with Git.
What you want to know?
Fuck, I’m old.
\documentclass{article} \usepackage{soul} \begin{document} I'm 19 and I know how to use \LaTeX, \LaTeX is more used in academia, they taught me \LaTeX in Uni, but a lot of other people just won't ever heard of it because is rare to find in other places, most technical degrees and even a lot of uni ones won't use it \st{even if it's vastly superior to word}. \huge \LaTeX rules \end{document}}I think you dropped this.
You have to excuse me, texstudio adds automatically the closing one.
I’m 40 if that helps.
I’m in that that as well. I’m my age™ everybody wrote their bachelor and master thesis in LaTeX 🤷
I become a software developer later in life and never had the privilege to go to university, so sometimes I’m out of the loop on older tech.
How did Latex compare to modern Git?
Latex is no versioning tool but a textsetting language. It outputs perfectly formatted Documents after building and takes care of aranging images, quotes and all the tedious stuff so after setting up your template you only have to care about content. It works well with git.
Not like word where adding an image fucks the whole formatting.
Interesting.
Yeah word sucks. I’m a software developer now and have to deal with Word and Excel more than I ever thought I would.
I’m a softwaredev too, we use this for our manual. Its writen in markdown, which we convert with pandoc to latex. We can use git for versioning and merging and the manuals always look very nice.
As a software developer, LaTeX makes writing documents feel elegant in the way good code is elegant. No more manually going back and saying things like “as shown in diagram 4” and updating the number when the number of diagrams changes; LaTeX can do that for you by referencing the object. Citations and bibliography are an absolute breeze to generate. It can generate various kinds of plots and diagrams themselves for you, making it much easier when you then need to make changes to it later.
With the right packages (think: code libraries) you can do all sorts of things. I like the
acrodefandaccommands which lets you specify a bunch of acronyms, and then the first time you use them in a document it automatically expands it to the full version, but uses the acronym on all subsequent uses. When writing code snippets, you can have it automatically apply the correct syntax highlighting for the language you specify; though this is admittedly a feature many markdown implementations also have.Well in this thread people were saying you can set up your own local git repository? What’s a newbie friendly way of doing that. I’ve watched videos and understand that git version control system but I can’t quite seem to grasp more than that.
I will answer this, I am sick right now but will return.
It is a pity that Markdown does not have the possibilities of Latex.
I learned latex by doing my engineering homework in it. I quit using latex because I kept doing my engineering homework in it and it turns out it sucks to do