Chris Downie

@cdownie

Mobile developer. Puzzle solver. Organizer for .

Missoula, MT
Vrijeme pridruživanja: studeni 2007.

Tweetovi

Blokirali ste korisnika/cu @cdownie

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @cdownie

  1. prije 2 sata

    Problem 23 of solved. Lua runs in 5.6s, Swift in 1.8 I realized I’ve been benchmarking my Swift solutions with debug builds. The release builds run so much faster without any other effort. Way to go, compiler.

    Prikaži ovu nit
    Poništi
  2. proslijedio/la je Tweet
    31. sij

    🥶 Cool Take When we lost visual richness in software, we lost a requirement to think about design with regards to how it looks. Everyone loved to parrot Steve Jobs’ famous quote “Design is how it works,” but what he said was much more nuanced. ⤵️

    Prikaži ovu nit
    Poništi
  3. proslijedio/la je Tweet
    3. velj

    It would be great if the Republican leaders in the Montana House of Representatives were as concerned about what Trump says and does as they are with State Rep. Garcia.

    Poništi
  4. 3. velj

    Problem 22 of solved in Lua (9ms) and Swift (50ms). 👍 Both languages have fast enough built-in sorts so this was pretty easy. 👎 My Swift solution stumbled upon a nasty compiler bug. Reported as FB7561652.

    Prikaži ovu nit
    Poništi
  5. proslijedio/la je Tweet
    3. velj

    Magic of surveillance capitalism indeed

    Prikaži ovu nit
    Poništi
  6. 2. velj

    Problem 21 of solved. Lua solves in 1.2s, Swift an _order of magnitude_ slower at 22.7s. I could probably spend more time making my divisors method faster, but I’m ready to move on. I spent way too long misunderstanding this problem.

    Prikaži ovu nit
    Poništi
  7. 1. velj

    Problem 20 of solved in Swift (182ms) and Lua (31ms). Neither language had enough precision, so I had to implement my own BigInt type. Kinda surprising there isn’t a BigInt in Swift already. Not surprised by Lua.

    Prikaži ovu nit
    Poništi
  8. proslijedio/la je Tweet
    29. sij

    I just had my eyes dilated, so I can’t read any text that isn’t comically large. I don’t know how to use a screen reader. I’ll be fine in a few hours, but this has been a fascinating journey into how well third-party iOS apps respect text size accessibility settings! (Thread)

    Prikaži ovu nit
    Poništi
  9. proslijedio/la je Tweet
    29. sij

    Code Reviewers - it's easy to go pure negative/nitpicking, even if you're using helpful/constructive language. if you see something you like, SAY SOMETHING. It makes people's days. Today I had a total in a PR.

    Prikaži ovu nit
    Poništi
  10. 30. sij

    Problem 19 of solved in Swift and Lua. I found my first novel use of pattern matching with Swift on this one.

    Prikaži ovu nit
    Poništi
  11. 28. sij

    Problem 18 of solved in Swift & Lua: I totally overcomplicated this for myself by trying an A* search. Ended up with a simpler solution. I really shouldn’t try to optimize things until I have a perf issue.

    Prikaži ovu nit
    Poništi
  12. 27. sij

    DJT and the RNC regularly send out requests for donations framed like surveys, with terribly written, terribly biased questions. But this one takes the cake. If news of an “Impeachment Scam” is Fake, then it’s not a scam, right?

    Poništi
  13. proslijedio/la je Tweet
    25. sij

    (A few) Ops Lessons We All Learn The Hard Way -- a Twitter 🧵:

    Prikaži ovu nit
    Poništi
  14. 25. sij

    Problem 17 of solved, in Lua & Swift. This wasn’t hard, just annoying. I did like the readability of both `#”and”` and `”and”.count` rather than hard-coding some string lengths.

    Prikaži ovu nit
    Poništi
  15. 25. sij

    Problem 16 of solved in Swift & Lua. Another quick runtime since both languages handle big numbers well.

    Prikaži ovu nit
    Poništi
  16. 24. sij

    Problem 15 of solved in Lua & Swift: Tree traversal took waaaay too long. I had to figure out a math-y way to solve it. Runs instantly in Lua, and in 2ms for Swift.

    Prikaži ovu nit
    Poništi
  17. proslijedio/la je Tweet

    Only 5 spots remaining in our and Bootcamp happening in February!👇

    Poništi
  18. 22. sij

    Problem 14 of solved in Lua & Swift. Memoization was a huge performance gain, even more so than Lua’s optimized tail recursion. It took Lua’s runtime from ~17s to 1s, and Swift’s from ~5s to 2s.

    Prikaži ovu nit
    Poništi
  19. 21. sij

    Problem 13 of solved: Swift & Lua seem to handle large numbers well, so the obvious approach solved it almost instantly in both languages.

    Prikaži ovu nit
    Poništi
  20. 21. sij

    Problem 12 of solved! The Swift solution runs in 0.4s vs Lua’s almost 2s. For the same style approach.

    Prikaži ovu nit
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·