• 3 Posts
  • 183 Comments
Joined 5 years ago
cake
Cake day: May 24th, 2021

help-circle

  • If you’re truly honest about wanting to improve your skills then do not use AI!

    Just write code. Any code! It doesn’t matter. Spend the hours problem solving and debugging and banging your head against the wall. That’s how we all learned and gained experience. But also reach out and seek help about specific problems you can’t solve.

    For a project idea, how about a program that uses the Lemmy API to scan resent posts for Python topics. It’s something that can start basic but can be expanded upon. Start simple by just scanning posts from the last day. Then expand by adding a configurable date range, scanning several communities, multiple topics, presenting notifications, etc.


  • This is cool and it’s nice to see some acknowledgement and self reflection.

    I actually like async Rust and I feel that they made the right decisions there. It’s amazing that I can use similar constructs for a web server as well as a small embedded board. But the low level Futures stuff does get hairy. I still don’t really get the relationship between Pin and Unpin, and any time I have to write a Tower Service by hand it feels arcane. Fortunately I rarely have to go down to that level.

    The tacit knowledge is interesting. Is there an ecosystem that doesn’t have that to some degree? Node and Python feel even worse to me, though I admit I don’t work with those as much. Still, if I ever have to look for a Node library, I get worried that I might be inadvertently installing some malware. That said, I am about to sit down with one of my juniors to start on a new Rust project, mainly because I want to help setup the initial crates (tokio, tracing, anyhow, clap, etc…). Efforts like blessed.rs are a good start. Or maybe there are some good “starter kits” using cargo-generate?



  • That’s a terrible take and its desperately trying to draw an equivalence where there isn’t one.

    I’d argue that the slop code creates more drudgery with having to constantly babysit the LLM. Never mind a new blog post every week about how your “agentic workflow” from last week is all wrong and you need even more infrastructure to wrangle the LLM. It’s worse than the way the JavaScript ecosystem used to be!

    Reading someone else’s code is challenging, but at least with a person you can ask them questions or debate.

    I guess I’m just someone who finds reviewing someone else’s work tedious, though a necessary part of the job.



  • I wonder how many of these folks just don’t know about the alternatives. I’ve come across otherwise capable developers who think git and GitHub are the same thing. People come to software from all sorts of backgrounds so I can’t blame anyone for not knowing.

    I also imagine that if people are aware, the activation energy of switching is too high. It’s more than just setting a new remote and pushing. You have to learn the new system, maybe migrate tickets, wrestle with CI, etc. For a hobby project it’s probably easier to shut it down and just go do something else. I also don’t blame them here. There’s more to life than open source, and its amazing people are able to contribute when they can.






  • Loooolll! I love them raising a stink about forking I’m another language. Go for it! Nobody cares and I’m sure it’ll reach feature parity by the time paru is updated. 🙄 And then mentioning Lunduke saying something negative about Rust. Isn’t he some wacko conspiracy/Linux YouTuber? That all made for a good laugh.

    Anyway, I really like Paru, but I’ve switched back to yay until they get a fix. Really not a big deal.







  • “Agentic Engineering”. No, it’s called vibe coding. AI bros are so desperate for legitimacy they make up fancy sounding titles for themselves.

    But this isn’t engineering. Engineering takes rigor and discipline and process and understanding… A lot of it is extremely boring too. The code itself is probably the easiest (and I’d argue least important) part of software engineering. These guys are burning down forests to poorly automate the easy part.

    I’m not saying that coding is easy in an absolute sense, but only relative to the rest of the discipline. A good engineer knows how to design/architect a system, understand tradeoffs, balance customer/user requirements with business needs, set up proper testing and releases, properly document everything, etc.