Google just deleted my developer account for inactivity. WTF. I had a published app on there, it was published earlier this year...
bersling
- 67 Followers
- 131 Following
- 105 Posts
Web Dev from Switzerland. Studied physics at ETH, then ventured into edTech and co-founded https://taskbase.com. In my spare time I'm working on a game for kids (https://toddler-games.com). Blog at https://tsmean.com. Expertise in Web Dev and specifically mostly worked with #Angular, #Svelte, #Kotlin, #MySQL, #k8s, #AWS
Conclusion for now: If it's something more involved, do it inside of the server. The API might be lacking functionalities, leading to roadblocks. Not something you'd want.
If you have a server with an API and you need to run a migration for parts of the data do you:
- write a script and call the API of the server?
- code the migration into the server so it runs e.g. on server start or on a specific API call?
- write a script and call the API of the server?
- code the migration into the server so it runs e.g. on server start or on a specific API call?
Started to pay a lot more attention to how I log/print in my scripts recently. If I'm working on something for a while it might as well give me nicely printed results each time I run it :)
And: Is there any petition going on somewhere?
Any thoughts on the 20 testers rule https://www.youtube.com/watch?v=bzhmgkuR0dU ?
A Team of 20 to Publish an App?! - THIS New Google Play Policy Change is CRAZY
Fortunately, coding is a superpower
document.getElementsByClassName("CodeMirror")[0].style.height = '1000px'
Why is a gist only 17 lines of code high and the height is not changeable?! Shouldn't that be a comment they've been receiving for years? Or am I missing something?
- Step 1: Open Github
- Step 2: check top left
- Step 3: be happy that you're not the only one deploying blatantly obvious bugs to production? :)
- Step 2: check top left
- Step 3: be happy that you're not the only one deploying blatantly obvious bugs to production? :)
Passing objects / data classes as function arguments instead of listing the arguments one by one has a couple of compelling arguments. You have to type less when you pass the thing through a chain of function calls. And you can also document the object, for example
data class(
// Extensive explanation why this property exists
val someObscurePropertyNoOneIsGoingToRememberWhatItIsFor
...
Then the probability that other devs find the documentation is high.
if you just pass the arguments through a chain of functions you're not going to comment on every function.