Elikya Bokanga

Day 1 of #100DaysOfCode - made a dice statistical calculator for some TTRPG ideas I'm bouncing around.

Day 8 of #100DaysOfCode - still haven't eaten my words on pointers, but goroutine channel directionality is a strange beast.

Day 7 of #100DaysOfCode - pointers and (de)referencing don't seem that hard. Let's see how long till I eat those words.

Day 5-6 of #100DaysOfCode - I want to like Go. I really do. But it has quirks that are really unintuitive. Ex. re: named return values on functions - for whatever reason arrays that fail to have items appended to them return []type(nil) instead of []type{}... why

Day 3-4 of #100DaysOfCode - Go is an interesting language, much like a cleaner JS. But I feel like its static typing is an ideal that the language tries very hard to find shortcuts around, almost as if it didn't even want to be statically typed.

Day 2 of #100DaysOfCode - started learning Go today, mostly messing around with install and config stuff, but the actual language strikes me a bit like JS

Day 1 of #100DaysOfCode - back on the horse

Day 34 of #100DaysOfCode - got the bugs out, time to clean up the code!

Day 32-33 of #100DaysOfCode - got caught in a debug cycle and decided to chill with some katas.

Day 30-31 of #100DaysOfCode - really starting to question the utility of OOP. Splitting up state across several files is a real exercise in managing complexity.

Day 29 of #100DaysOfCode - learned a neat problem with #javascript : `typeof null` returns an object! So I'm using `instanceof` or `[object].constructor.name` (minus the []) to use it in control flow.

Day 28 of #100DaysOfCode - redoing APIs are a pain

Days 26-27 of #100DaysOfCode - purged a ton of code, rewrote a ton. Feeling a lot better about the design now though.

Day 14 of #100DaysOfCode - happy Thanksgiving fellow challengers

Day 13 of #100DaysOfCode - pounding headache, pounding out code.

Day 12 of #100DaysOfCode - why do I always pick big projects?

Day 10-11 of #100DaysOfCode - rewriting all my classes. I underestimated game design. Props to the pros.

@muulsh @quibbler @mbal6611 @FrankDanconia6 @engineers_feed I think those only work for single word passwords. An attacker wouldn't get positive feedback for getting the first word, so it wouldn't be able to leverage that into the rest.

It’s password awareness Friday. Send us your password and we will tell you if it’s strong.

@mbal6611 @FrankDanconia6 @engineers_feed I posted this earlier, but bears repeating.

Day 9 of #100DaysOfCode - figuring out how to properly nest abstractions