FYI: Another feed reader I built (called pluto with sqlite as feed / data storage) see https://github.com/feedreader - used by OpenStreetMaps Blogs, Planet KDE, and others.
PS: For the (ongoing) struggle (trying) to "normalize" the RSS and ATOM feed formats (or JSON Feeds) see the feedparser gem - https://github.com/rubycocos/feedparser
Why not latex? Why not the best of both worlds? Anyways, see latext and markdown compared - https://github.com/mundimark/markdown-vs-latex In evolution simpler wins. The beauty of the paragraph syntax is an empty line, for example! And yeah for sure - the image syntax in markdown is a big FAIL and there are easier alternatives upcoming (out there waiting for the big time) - see https://texti.github.io - and image and figure "macros" - that is - built-in templates, for example.
May I introduce Texti (Markup Language) - Text with Instructions (.texti) - Structured Documents in Text with Formatting Conventions - that tries to offer the best of all worlds - that is - markdown / textile / mediawiki markup/down / latex and more. See https://texti.github.io PS: An "important" building block missing in markdown / textile is built-in templates a la mediawiki markup/down. Lets you add "macros" for images or figures and so on (and much more). Extension and evolution is key - as always - and wins out in the long run.
FYI: New ideas first presented are always very confusing. Let it sink in. Note: The page is public - thus, if I may return the favor - change the confusing private to public in your sentence (or is that "knee jerk private commentary?").
PS: Let me add more context - The top-linked Textile Markup Language is a documentation website. Textile markup/down is history and FAILED - thus - the next step is what can we learn from the fail - what are the good, bad and ugly parts? what was missing and so on. Now how do you "fix" textile (or markdown)?
For more context let me add / point out the side-by-side samples (texti vs markdown vs latex vs wikipedia markup), see https://github.com/texti/texti.github.io/tree/master/samples using the Wikipedia article on markup as an real-world sample.
a) awesome. b) please increase the default font size of that doc. c) please consider moving the exposition to the end and just jump into the good stuff about how it works and what's different. Perhaps a short intro like "Texti is modern markup. Think Markdown and Wikimedia markup had a baby. Here's how to do all the things..."
Thanks. Note this text is not a commercial or ad. My philosophy is function over form wins. Period. Comments and critique always welcome. If I may return the favor - do NOT use the word modern - as in say 5 or 10 years - that may read different. Do NOT upcase markdown - it is today a generic term / word. The had a baby "idea" is stupid. The idea is about evolution and adding AND yes, deleting and forever changing and so on. Anyways, here's the source (w/ public domain - no rights reserved dedication) - https://raw.githubusercontent.com/texti/texti.github.io/mast... you are more than welcome to publish your own teaser / promo / analysis / opinion.
Here's a real-world story of getting "exited" of my humble self - more a programmer (or code monkey) than an "engineer" really - see The Strange Case of Mammad Kabiri @ Uniqa Software Service. [1]
You should rename the article, I guess. Like this, it my first impression was that it would be another one of those posts where some random outsourcing employee complains that Google didn't hire them.
How about: "Wage theft by Uniqa Software Service and harrassment by Mammad Kabiri"
It might also make sense to point out that this is an EU court, because everyone knows that means worker protections actually have teeth. In the US getting fired like that is no issue in at-will states.
"EU court trial: Wage theft by Uniqa Software Service, Harrassment by Mammad Kabiri"
That's a good summary in my opinion.
Also, unrelatedly: Your text reads to me as if you could gain by improving your self-marketing. "code monkey" doesn't exactly sound like "that one guy we'll treat super nicely because we are afraid he might leave". But you certainly want to be in the latter category in your manager's mind. And chances are, after 10 years of working, you will have invaluable experience that helps your team. So it's probably mostly a matter of advertising your skills correctly.
FYI: I help out with the Ruby Pixel Art Week 2021, April 19th to April 25th - 7 Days of Ruby (Graphics) Gems.
The Ruby Pixel Art Week 2021 presents a new Ruby graphics library every day from April 19th to April 25th, see https://planetruby.github.io/gems
FYI: Here's my little minimialist starter kit called Hello, Minima! - Get Started w/ GitHub Pages (Jekyll) in 60 Seconds using the Minima (Gem-Packaged) Theme [1].
PS: For the (ongoing) struggle (trying) to "normalize" the RSS and ATOM feed formats (or JSON Feeds) see the feedparser gem - https://github.com/rubycocos/feedparser