• 1 Post
  • 88 Comments
Joined 1 year ago
cake
Cake day: August 7th, 2023

help-circle

  • Yep, programming is fun but working as a programmer not so much. For me writing software is a creative activity. It’s fun to come up with problems and find solutions for them. In my personal projects I decide what problem I want to solve, choose the technology I think will be fun to solve it in and then come up with a solution I like.

    At work you are usually handed a problem you don’t care about (we’re decommissioning X, you don’t have to know why, just change everything to use Y), the solution is described in detail by someone else and you just have to turn it into some code using 5-10 years old stack.

    Fortunately at my current job I mostly do projects without much technical oversight (proof-of-concept type project) so I can choose how I want to do then. I dislike the company culture but I know that moving somewhere else would mean going back to boring coding agian.



  • ExLisper@linux.communitytoProgrammer Humor@lemmy.mlDateTime
    link
    fedilink
    English
    arrow-up
    24
    ·
    10 months ago

    OMG, it’s so trivial. What you do is when T2 happens you send an atomic clock back in time to T1 and start counting till T2 happens again. If T1 and T2 happen in different locations you send two entangled clocks and collapse the state on T2 clock when the event happens measuring the exact moment on T1. How is this an issue?






  • I though the same but I tried Tauri and it makes sense. Unlike electron you’re not shipping the entire browser with your app and the the low level stuff is just rust so the integration is nice and easy. And using webview for UI? Why not? The reactive libraries are actually nice to work with, it’s easy to customize, you have all the tools to inspect/debug your code. It’s definitely better then trying to fit GTK into rust.


  • I tried Flutter and hated it. It was buggy (there’s thousands of post on the internet saying that you have to do ‘rm ios/Podfile && flutter build ios’ and similar. the build breaks often and standard solution is ‘turn it off and on again’), the components library is too verbose and not nice to work with, the support was bad (as in open a bug report with example repo and they would react after 6 months) and everything that’s not ‘hello world’ was complicated or impossible (like writing tests). I’m definitely not using it again.


  • Each org is different. There are organizations doing agile in a shit way, there are organization that are shit because they don’t do agile and there are some that do OK because they take out of agile just what they need. In my first job they would write all the requirements up front, agree the price, sign a contract and then discover crucial functionality was missing. So they could either deliver useless product and piss off the client or do some extra work for free. It was shit. In my next company everything was nicely divided into sprints but the process was so overgrown working there was super boring and most project didn’t even finish, they just got cancelled somewhere in the middle. My current company mostly lets teams organize themselves and is using agile to monitor progress and react if something gets delayed. It’s mostly fine. Agile is not the problem and it’s not a universal fix. You simply have to be smart about which or it to use and how.