• 0 Posts
  • 5 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle
  • My only point on the compass being a better representation is that it acknowledged a problem. That’s not to say it’s a good representation.

    I think it’s unhelpful to say that a step toward more fidelity is the same level of bad, though. Even if it’s the tiniest step, it’s a move in the right direction by pointing out that a single line isn’t sufficient.

    In reality, it would be more like a series of lines on different topics weighted differently by an individuals priorities so no singular generic representation will ever be truly good enough.



  • Why isn’t purchasing the part through Apple enough?

    And also Is the consumer not allowed to assume the risk of going through after market repair that you seem to be concerned about?

    This issue has always been about Apple trying to force older iPhones into obsolescence. They want the freedom to eventually say that no more parts exist for that device so you’ll have to upgrade. If repair shops can leverage broken phones to repair other phones, that extends the life of the device part Apples plans.

    Most people will continue using older phones as long as they can because they don’t need the latest phone.



  • It depends on the company for how much any developer role will be responsible for, but a backend developer would typically be responsible for anything that isn’t the user interface. I’m unsure how often the web app statement is true, honestly.

    As a lead backend developer I’m responsible for the overall scalability of the platform I work on. Scalability ties to performance, throughput, and maintainability. In my specific position, I tend to leave performance of the code to the members of my team who are implementing a feature while I am building designs that focus more on throughput and maintainability.

    This obviously requires a knowledge base of the language I’m working in, but also various mechanisms for distributing work across multiple services and locating bottlenecks in a platform to target for improvement.

    I currently work in a combination of Python and Rust. My last position was Golang. Cloud infrastructure comes in to play quite often. AWS knowledge will be really useful in this field. Some relationship database knowledge will go a long way. Learning how to properly build and use a cache.

    Overall, I would say it’s not repetitive in the long term. Early on it might be a lot of hammering out other people’s designs but you get a greater degree of flexibility as you progress and learn more.