Reader9
Ready Player One has the worldwide virtual reality system owned by a single corporation with one shareholder, and
spoiler
change of ownership determined by being the best at video games and trivia
Mark Zuckerburg: “people will love it!”
Cool project and post! There’s also !flashlight@lemmy.world if you’d like to cross post.
gets hot enough to burn you if you leave it on for too long
That Fenix looks like a reliable light and is designed with temperature regulation but the limit might be pretty high and of course it is being used in an enclosure.
I can see you like Anduril! Except for the wurkkos ts12.
How do you like the brass ts10? Seems like a great value and is on my list to potentially get.
Sticking with the 14500-theme, my first hank light might be a D2 if I can settle on an emitter combo.
I am learning Python, R, and SQL
SQL is an excellent skill to invest in. Even though your current role doesn’t allow you to use it, there’s no substitute when pulling data from a relational db.
It sounds like you’re currently focused on data quality. Automatic data quality checks are common features of (good) data workflows so this could be spun as relevant experience if you end up seeking a role writing data transformation code.
Feels odd for admins be able to prevent users from seeing content
My understanding is those admins aren’t just allowing users to view it but also allowing copies of the federated data to be stored on the server those admins are responsible for, so for certain types of content it seems really important to be implemented in this way.
We can’t test yet, we’re going to make changes soon
This could be a good opportunity to introduce the concept of test-driven development (TDD) without the necessity to “write tests first”. But I think it can help illustrate why having tests is better when you are expecting to make changes because of the safety they provide.
“When we make those changes, wouldn’t it be great to have more confidence that the business logic didn’t break when adding a new technical capability?”
You shouldn’t have to refactor to test something
This seems like a reasonable statement and I sort of agree, in the sense that for existing production code, making a code change which only adds new tests yet also requires refactoring of existing functionality might feel a bit risky. As other commenters mentioned, starting with writing tests for new features or fixes might help prevent folks feeling like they are refactoring to test. Instead they’re refactoring and developing for the feature and the tests feel like they contribute to that feature as well.
candle mode
This might be the problem, candle mode has no thermal regulation if I remember correctly.
Glad you weren’t hurt and hopefully the cell can be rewrapped.
Focusing on code coverage (which doesn’t distinguish between more and less important parts of the code) seems like the opposite of your very good (IMO) recommendation in another comment to focus on specific high-value use-cases.
From my experience it’s far easier to sell the need for specific tests if they are framed as “we need assurances that this component does not fail under conceivable usecases” and specially as “we were screwed by this bug and we need to be absolutely sure we don’t experience it ever again.”
Code coverage is an OK metric and I agree with tracking it, but I wouldn’t recommend making it a target. It might force developers to write tests, but it probably won’t convince them. And as a developer I hate feeling “forced” and prefer if at all possible to use consensus to decide on team practices.
Time zones are an endless source of frustration, this one doesn’t sound too bad though:
Going forward, all timestamps in the API are switching from timestamps without time zone (
2023-09-27T12:29:59.113132) toIStimestamps (e.g.2023-10-29T15:10:51.557399+01:00orZsuffix). In order to be compatible with both 0.18 and 0.19, parse the timestamp asISand add aZsuffix if it fails (for older versions).
