Hacker News new | past | comments | ask | show | jobs | submit login

Agreed, after a year or two, blogs become your experience logs to prove experience and credibility once the landscape is killed by GenAI slops and SEO scams.

Anyone can generate a big portfolio of projects these days(be it graphics, video, software, writing etc) but blog posts from 2023 and before are proof and undeniable.






> Anyone can generate a big portfolio of projects these days(be it graphics, video, software, writing etc) but blog posts from 2023 and before are proof and undeniable.

I always read blogs if people include them in resumes.

It’s really cool when an applicant has a blog with unique and interesting content, but I can’t remember this happening without us already having been very impressed by the candidate’s resume.

More commonly, blog content was ambiguous about the applicant’s skills. For example, when someone applies to an embedded job but has a blog of beginner level Arduino projects, is that because they’re an expert creating tutorials for beginners, or because they are a beginner and these entry-level projects represent their skill level?

I also think people greatly overestimate the idea that someone will LLM their way into a great blog, and they greatly underestimate the difficulty of forging timestamps. Even git timestamps are easy to fake. Your interviewers aren’t going to scrutinize the Wayback machine for evidence, but not being indexed isn’t proof that it wasn’t there anyway.


> is that because they’re an expert creating tutorials for beginners, or because they are a beginner and these entry-level projects represent their skill level?

You can tell by reading one of them though, right? For a subject I'm an expert at, I can tell the difference between an expert talking about the basics, and a beginner doing the same.


If they write a lot, then you can.

But in my experience reading a lot of applicants’ blogs, it’s rare to even find a recent post. The most common scenario I see is that the most recent posts are 3-10 years old. Even if you can get enough information out of their blog, you’re getting at best a snapshot of where they were a long time ago. The truth is that often people blog the most when they are beginners in a subject.

I guess what I’m trying to say is that the ideal optimal blog that people imagine writing is an extreme rarity. I’ve seen so many people start blogs with high ambitions but then the farthest they get is a couple posts that are now so old that it barely corresponds to their current resume level of skills.

So you’re left doing a lot of guessing and extrapolating.


It's probably not the only input you want but, generally, I agree with your comment especially across a number of posts.

Maybe it’s different in embedded, but as a mech e: any moderately complex hardware project will likely cost orders of magnitude more than a software project to prototype and manufacture. Off the self electronic parts have become much cheaper, but if you need more than some plastic, 3D parts it’s still expensive.

This isn’t true at all. Even custom PCBs are so trivially cheap that you can get 4-layer boards from China shipped for under $10. An ESP32 module is a couple bucks.

Electronic projects are extraordinarily cheap right now. I’ve built moderately complex PCBs for less than the price of a nice dinner.


A four layer board is not “moderately complex”, it’s child’s play. IMO moderately complex is in the 10-20 layer range with controlled impedance, buried vias, etc. or a mechanical assembly with hundreds of parts.

Everything definitely has gotten significantly cheaper than when I started working in mechanical/electronic engineering 15 years ago but a moderately complex board with assembly is still hundreds or thousands per board on short (1-2 week) notice. That’s what the GP means when they say that hardware prototypes are orders of magnitude more expensive (sans NRE) and I’m pretty sure they’re talking about the much more expensive mechanical side too, which also had gotten cheaper but not overwhelmingly so.


I've been treating public Git repository commits in the same vein - a receipt of incremental changes that show that an individual can do some programming. Granted this is not fool-proof - like all things that are complex, it needs to be evaluated with a suite of other factors and conditions to be determined valid. A website written in a personal voice is one of these factors.

I often wonder if work experience on your resume pre-2023 will become a hot commodity for employment in the coming years.

A dark pattern on your self hosted blogging website is to backdate blog posts and make yourself seem very good at predicting future trends.

There is no reason why you have to write a blog over a long period of time, you could quickly pump out several blog posts and link to them to establish credibility quickly.


We need better timestamping services for this.

I tried to write out an initial spec here, but I haven’t been able to write any implementations yet: https://github.com/sebmellen/proof-of-origination.


> We need better timestamping services for this.

If I were to write a dozen blog posts today, and then straight up dump them on my blog, dating each of them so they're spaced roughly evenly since Jan 2021 to today, and start each of them with a preamble saying "I wrote this in my journal around [backdated timestmap]; publishing it now ([real timestamp]) as part of my 2025 blog revival commitment" - what would you say then? This little preamble explains both the sudden appearance and lack of any prior traces on the Internet corresponding to claimed creation dates. Are you going to call me a liar?

No, if someone with even half a brain wants to fake expertise this way, you won't be able to tell. If anything, what will give them away is anachronisms in text. Like idk. an off-hand remark about ChatGPT in a post dated 2021 could make you wonder.


But you're still a liar. And 'calling you out' isn't a prerequisite to (correctly) suspecting it.

There's this on the Bitcoin blockchain: https://opentimestamps.org

I guess you can use a third party like archive.org, if the blog is crawled by it, the owner doesn't get them to delete it, and there is no politically motivated revisionism going on based on the archive.org maintainers.

I would be suspicious of a reasonably popular blog claiming to have predicted stuff and not being able to back that up with an archive.org capture (or raw scraper data), though I guess it is somewhere where storing a hash on a blockchain may offer some benefits for edge cases.


If some one is determined to find out the authenticity then it’s possible right? Like Waybackmachine or similar tools?

Lots of plausible deniability

If I find 10 backdated articles appear out of thin air in Waybackmachine I'm not going to ask the author to explain it. It just lowers their credibility in my mind and I move on. I'm not interested in proving to them or in a court of law that they backdated articles.

Links submitted to Reddit or HN then a bit work as proofs of the publication date

since one cannot backdate timestamps on Reddit and HN. Hmm but you can still rewrite the content a bit


Yes this only proves you had something on a certain date, but not that the content has been unchanged.

if you're that popular, there should be some history in archive.org or archive.is

>"Anyone can generate a big portfolio of projects these days"

LOL. I could easily do it "back in those days". The difference is that in my particular case (I specialize in developing new software products for clients) I also have long list of names with actual phone numbers, emails, addresses etc. So anyone can call and verify.

Never blogged. Have no time / desire




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: