I'm a long time SWE and in the last week, I've made and shipped production changes across around 6 different repos/monorepos, ranging from Python to Golang, to Kotlin to TS to Java. I'd consider myself "expert" in maybe one or two of those codebases and only having a passing knowledge of the others.
I'm using AI, not to fire-and-forget changes, but to explain and document where I can find certain functionality, generate snippets and boilerplate, and produce test cases for the changes I need. I read, review and consider that every line of code I commit has my name against it, and treat it as such.
Without these tools I'd estimate being around 25% as effective when it comes to getting up to speed on unfamiliar code and service. For that alone, AI tooling is utterly invaluable.
> ... Feedly that pretend to care about RSS but layer on features unrelated to the protocol
I've been using Feedly since Google killed reader, and while I like the RSS functionality it offers, I do agree that they've slowly been adding more and more features I don't care for.
Maybe it's time to migrate to something like TFA suggests.
I also agree with your other comments; it's huge a shame.
author here, thx for pointing these out! I was simultaneously working on some CSS for my blog on localhost and when I looked up some references to older articles to put in my post, I looked them up in the version of my site that was running locally and forgot to change the links lol. Whoops. Fixed now — thanks again!
I've been using McFly [1] recently, and like it a lot.
> McFly replaces your default ctrl-r shell history search with an intelligent search engine that takes into account your working directory and the context of recently executed commands. McFly's suggestions are prioritized in real time with a small neural network.
the neural network is pretty broken. It prioritizes things that I did weeks ago over a command that I just ran 20 times. Be a bit critical of it, I actually found it fairly terrible.
I know it's open source and people working on it might be reading this so let me apologize to you personally and please don't take this message as discouragement. I know how demotivating one bad review can be. It just wasn't working for me.
As was also pointed out in the TFA, while you may not be "marking people down" because of unfamiliarity with syntax, an interviewee who has more experience with the language (and it's debugging tools) used in the interview will have an inherent advantage over someone who isn't as familiar.
"Think of how stupid the average person is, and realize half of them are stupider than that."
reply