About topic on capitalization at 1:50, when I was 12, I tried to download mods to play Minecraft and none of them worked even though I followed every instruction. I was able to fix the issue only by changing my computer language to be English. Many years later, I realized why it only happened to me, "Oh......... Makes sense..............................The capital İ"
sometimes I can manage to get enough motivation to play some more kotlin in my pet projects, but I still feel I will scared of stuffs gonna happen there; I would only comfortable with my familiar skills or framework; what should I do
Daylight Saving Time adds more light time to evenings in summer, not in winter. It makes winter days go dark earlier. At least in northern hemisphere. I never thought about how it works in New Zealand. I guess it's much crazier there.
@@h4m74ro you do it for everything, no exceptions, calendar or not, if you need to do some sophisticated crap like fintech tends to do, or simply say go to last day of month... feel free to temporarily convert to date time or jodat time whatever but your main format should always be timestamp. Put assertions that validate that your modifications make sense but the moment you start using Date alike formats in Dbs or pass them around everything goes to shit. Once some legacy is created using that it never goes away.
@@krellin User sets a alarm at noon 12:00. When you save that as timestamp instead of 12:00, it will be wrong after changing time zones. Or user saves a meeting in his calendar for next year 1st of july at 10am and is based in Germany, that is 2025-07-01T10:00:00+02:00. Again, if you would use timestamp instead, you have a bad time when unexpected things happen, like EU decides to abolish daylight saving time. Even the leap seconds every few months will cause a small discrepancy. I'm not saying, save Date objects, only string representation in ISO format. That works wherever you are and on any device.
About topic on capitalization at 1:50, when I was 12, I tried to download mods to play Minecraft and none of them worked even though I followed every instruction. I was able to fix the issue only by changing my computer language to be English. Many years later, I realized why it only happened to me, "Oh......... Makes sense..............................The capital İ"
kotlin is my favorite programming language :)
Same here ❤
so much better than java!
sometimes I can manage to get enough motivation to play some more kotlin in my pet projects, but I still feel I will scared of stuffs gonna happen there; I would only comfortable with my familiar skills or framework; what should I do
And you use it to....? Andoird Dev? Back end server?
@@tk1576 So you use it to replace those domains which use java before? Or you use it every where with kotlin/native?
Funny and attractive talk, love this one!
Daylight Saving Time adds more light time to evenings in summer, not in winter. It makes winter days go dark earlier. At least in northern hemisphere. I never thought about how it works in New Zealand. I guess it's much crazier there.
Experienced engineers don't mess with timezones and use a timestamp long, do all the compute with it and then convert to strong in front end
If possible, do it. But for something like calendar apps or future events, don't do it.
@@h4m74ro you do it for everything, no exceptions, calendar or not, if you need to do some sophisticated crap like fintech tends to do, or simply say go to last day of month... feel free to temporarily convert to date time or jodat time whatever but your main format should always be timestamp. Put assertions that validate that your modifications make sense but the moment you start using Date alike formats in Dbs or pass them around everything goes to shit. Once some legacy is created using that it never goes away.
So that you set your alarm -- when flying -- to 7am before your phone realized you're crossing 3 timezones, only for it to ring at 10am.
This is the way. I have spoken.
@@krellin User sets a alarm at noon 12:00. When you save that as timestamp instead of 12:00, it will be wrong after changing time zones. Or user saves a meeting in his calendar for next year 1st of july at 10am and is based in Germany, that is 2025-07-01T10:00:00+02:00. Again, if you would use timestamp instead, you have a bad time when unexpected things happen, like EU decides to abolish daylight saving time. Even the leap seconds every few months will cause a small discrepancy.
I'm not saying, save Date objects, only string representation in ISO format. That works wherever you are and on any device.
I moved from swift to kotlin for my leetcode and figured out how strong is Kotlin , never discovered this during my last 4 yrs with kotlin in android.
I really want to use kotlin or kotlin/native to replace javascript in web, and rust in wasm/wasi/system layer, so coooooool
oh no date and time always scares me ngl
7:15 the day that never existed 💀💀💀
uppercased(), lowercased(), capitalized(). There you have it where is my job at JetBrains
That would result in
- UPPER CASE
- lower case
- Capital Ized or Capital ized
@@shadowpenguin3482 or Capital İzed but just in Turkish
Short answer: it is hard. Like anything!
Kotlin has fun
TL;DW: Locale