No screenshots of code. I don't care if it's not syntax-highlighted, but I would like it to be in plain text, hopefully fixed-width.
If you're going to reference another blog, please include the relevant information in your own blog before the linked site goes down and I have to hope that site's owner didn't block archive.org from indexing it.
I'd like comments enabled, but I know some people have a hard-line stance against it (I was once told, "oh, you're thinking of a forum" when I suggested a developer add comments to their blog). Sometimes people smarter than me comment on my blog, and that adds value to my post when it has incomplete or incorrect information.
We don't always want to copy everything, we sometimes want to test out specific lines or what not. Don't mess around with how the select option works.
Not that I disagree but isn't there a security risk with code that can be cut and pasted?
Yes if the blog author is malicious and the copy-paster inattentive. Don't even need an inattentive user if it's a command pasted in a terminal that will interpret the newline as <enter>.
Epiphany is a crossover of Jupyter notebook and Medium.com,
Not only can you write text, you can also program on it, to create interactive examples, see:
In addition to interactivity, Epiphany implements version control, forking and pull request. You can collaborate with others just like you do on github.
An article will have two timestamps, Create time and last modified time. More than that, you can see the entire revision history.
Source code is in text and syntax highlighted.
It also has the social publishing feature as seen on Medium.
Finally, users own their content. Epiphany has a download button to allow downloading all blog data.
The format used by Epiphany, unlike that of Jupyter, is in plain text and is human readable.
disclaimer: I made Epiphany
I imagine you didn't notice this due to it being specific to my screen size (I'm on a macbook, I'm guessing you're using something else?)
I will resolve the issue this weekend.
I don't think the GitHub for the project is updated but from now on when I notice things I'll raise them as issues there :)
Also, not just blogs but everything ever posted online.
"17 minutes ago."
Or the top voted story on Oct 8, 2007 https://news.ycombinator.com/item?id=64795
Created used to show the number of days (I remember passing 3650), and now it shows the date. So the change was within the last year.
That or they think it gets people thinking they post more regularly than they actually do.
But yeah, agreed. Especially given that software development is a rather time sensitive field, and what works/happens to be best practice at one point may not be so further down the line.
A timestamp is useful for rapidly-cycling content, especially comment threads. If you're posting content less often than daily, a date stamp is sufficient, though if your site has multiple posts daily, go with timestamps.
"Sufficient granularity to distinguish content" should be your guiding principle.
I hate to be so negative but the internet is awash with bad coding advice (and the same code copied from vid to blog and back again) that seems like resume fodder more than helpful.
The worst thing about learning is reading a post long enough to realize the other person is a noob too and their code is a malformed mess that the blog author doesn't really understand.
Same thing has happened on my blog, I have some super old Pentaho configuration posts, and every once in a while I get an email from someone saying my code is not right but they were able to make it work with some changes. Hence, I leave it up there.