Reflecting on WikiTok
aizk.sh
aizk.sh
And with regards to AI taking jobs - it obviously will become a serious problem in future. But being a doomer right now is like lying down in a parking lot waiting to get run over - you're surrendering to a pointless outcome while the rest of the world keeps moving.
Inspiring to see you take on a different career path and go for it, I feel i'm on a similar journey right now, thanks for taking the time to write it up.
Yes, precisely. Maybe one could (re)make something using LLMs without understanding a thing, but that is as good as copy pasting from SO without understanding.
I'm sure there are a large amount of programmers who do this quite often..
So... almost all doomers?
This phrasing seems to suggest they think they invented the idea of "TikTok but it's Wikipedia". I see the author is OP, so my suggestion might be to consider rephrasing a bit as it comes off a bit accusatory.
I did try my hand on this project after seeing this bare-bones viral version. (I had the same idea in my notes app dated a couple years ago.) I went a different route, opting to pre-parse wikitext via my own API to deliver the app an AST that can be rendered natively & prettier than your standard Wikipedia page. Not a fun format to parse. Not fun at all. I don't recommend it. And it took significantly longer than 2 hours and was never released, so props to the author for turning this project around so fast.
Am I missing something, it comes off as the precise opposite to me? OP wrote "I built X, but the idea came from this source" basically, acknowledging they built the thing but the idea came from somewhere else.
The author is giving credit. Literally the opposite of your interpretation.
> I had the same idea in my notes app dated a couple years ago.
On the other hand this seems as if you now want to claim to be the inventor of the idea?
I built it and marketed it, but the idea came from some tweets that were gaining momentum.
https://www.aizk.sh/Isaac's%20Resume.pdf
Also vibe coding is useless without marketing skills, deployment skills, distribution, social media skills, etc.
I guess they'll learn it as they come across it? "Oh Claude, my code is almost like a plate of spaghetti, how can I make it easier to add new features without breaking something else?" "Dear user, here is what technical debt and unit tests mean: ..."
Besides, all of us self-learned programmers mostly learned about those things the hard way as well, by experiencing the real drawbacks of not caring about such things until too late and stuff is already up and running with real users.
“Random” is an algorithm. It just says that the next article you should read has no relationship with anything you’ve read before. That is a point of view. It’s good for an “explore” phase, where you want to expose yourself to as much variety as possible.
But eventually most people want to “exploit” their impressions from before. Just like I don’t want to always roll the dice on restaurants, sometimes I want to go back to one that I know is good.
But civil has serious issues (very low pay for how high the legal liability is).
If you search for jobs in civil you'll see hundreds of civil engineering firms are desperate for people to hire - it's similar to accounting where there's a mass exodus.
That may be a blog post in and of itself, why that industry is struggling and what that means.
Also the pay as a civil engineer with 3 years of experience was roughly half what I ended up making my first year as a software engineer.
> And with regards to AI taking jobs - it obviously will become a serious problem in future. But being a doomer right now is like lying down in a parking lot waiting to get run over - you're surrendering to a pointless outcome while the rest of the world keeps moving. There's still so much to build and accomplish.
I never used it, Yeah I know it exist but who tf use that???? and I'm considering myself "techy"