Self taught developer

Previously known as @[email protected]

Come hang out with me on Mastodon

Check out my blog, where I write about what I have learned

  • 14 Posts
  • 29 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle





  • ishanpagetoBlogging[Museum of Alexandra] EveryoneShouldBlog.txt
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    I deeply resonate with the sentiments in this article. It brilliantly articulates the topic in a way that I didn’t have the language for.

    It’s more important than ever in today’s homogenized internet monoculture to advocate for such things, especially for those outside the tech sphere. Great read!










  • I agree that from a completeness point of view, the official manual is better (I’ve linked it at the bottom of my post as well), however I’d love to hear your specific thoughts about why you feel this particular article is not good- I’ve tried to include fully interactive examples for the most common tasks I find myself doing with jq everyday. This feedback will help me improve my own skills as well, so I would appreciate it very much.









  • ishanpageOPtoProgrammingDear past me, use the flags
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 year ago

    The scenario is not ficticious. It’s taken straight from my first job, but I had to leave out specific details. The application being developed had something to do with DRM, so that might explain the weird requirements.

    The lesson is that sometimes business will require you to force users to update their version, and/or enable specific features for specific subsets of users. So you should have such a mechanism in place before it is required, otherwise you will end up doing hacky things like breaking the server to do what needs to be done.

    Systems such as these are actually fairly common in enterprise, but since it was my first job, I had not planned ahead for this because I had no idea.




  • ishanpagetoPHPConsume Symfony messenger messages in Go
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    This is great! I’ve done something similiar for Laravel in the past.

    What I’ve noticed is that as projects move forward in their development cycle, something like this often becomes necessary for certain functionality to require services to be factored out and then worked on by separate teams.