Hello Friends, I've been kicking around this Slac...
# introduce-yourself
w
Hello Friends, I've been kicking around this Slack since roughly the get-go, since Steve Krouse started the FoC podcast, since before the introduce-yourself channel, so I've never introduced myself properly. You'll most often find me sharing Rubyisms, mixed reality musings, spacial computing speculations, and the rare Aspect Oriented reflection, while being mostly busy writing little, tricky Rails apps for running big auctions. What with a good chunk of 5G spectrum allocated and 6G only a glint, I have the chance to dedicate some proper time to FoC projects. I want to work on something! Who is looking for a comrade, a consultant, a hired hand, or to just chat? Most anything and everything I see on the FoC Slack matches my interests remarkably well. Most recently, in the process of distilling lessons learned from fourteen years of modeling the domain of umpteen slightly yet significantly different auctions, a shockingly beautiful conceptual crystal sublimated, a not-so-future-required technique for leveraging data's functional dependencies to make long-distance object referencing reasonable. For instance, with
the.package_bid = some_package_bid
, we can talk about
the.price
,
the.bidder
, even
the.previous(:round).price
short for what might usually amount to going up and down a tree:
Copy code
some_package_bid.area_bid.round_bid.round.previous.
  round_bid(some_package_bid.area_bid.round_bid.bidder).
  area_bid(some_package_bid.area_bid.area).
  package_bids(some_package_bid.encumbrance_level).
  find{_1.option == some_package_bid.option}.
  price
šŸŗ 3
āœ‹šŸ¼ 1
āœŒļø 1
šŸ‘‹ 4
āœŒšŸ¾ 1
āœ‹ 1
w
We should chat Daniel. The code explorer looks really cute. I'm reminded of Code Bubbles http://cs.brown.edu/~spr/codebubbles/ and Code Canvas https://www.microsoft.com/en-us/research/project/code-canvas/, both from more than a decade ago now. 😳 Clicking around, I have a few questions immediately: • What's with the extra brackets in conditionals e.g.
else {{showMessage(PICK_EMPTY_CELL, player)}}
? • In the "Search functions by name" field, if I write "turn",
winInColumns
matches. I have no idea why. • I find the asymmetry between the CALL TREE area and the main area a little jarring. I mean in the CALL TREE, a function can be shown, hidden, or unlisted whereas in the main area, a function can be shown, collapsed, or unlisted. Honestly though. This is very neat. I like the mouseover references. I see a lot of potential. I love how the URL encodes the view state. That is slick.
d
Code Bubbles is a big influence for sure, thanks for reminding me about Code Canvas I should see what makes sense stealing incorporating
• What's with the extra brackets in conditionals e.g.
else {{showMessage(PICK_EMPTY_CELL, player)}}
?
A bug šŸ˜•
In the "Search functions by name" field, if I write "turn",
winInColumns
matches. I have no idea why.
šŸ¤” That's weird, I'm using a fuzzy search package, I'll take a look into it
I find the asymmetry between the CALL TREE area and the main area a little jarring. I mean in the CALL TREE, a function can be shown, hidden, or unlisted whereas in the main area, a function can be shown, collapsed, or unlisted.
Yeah the UX is pretty much WIP. So I have many ideas of interactions but I'm still not sure which ones are useful šŸ˜… Close to the right, close, collapse, show/hide will have really different use cases, but I can't be sure which ones to keep until I test them with a real project. Which takes me to the current work. I'm using the GitHub API to get the information, but it has a rate limit of 50 req/hour, so I haven't been able to play with a medium size project to see what's useful. Right now I'm working on the backend to add authenticated GitHub API requests which will increase the rate limit to 5,000/h. Anyways, I'd love to chat @wtaysom, are you available during the weekend?
w
UIs usually are a work in progress! I just thought it might be helpful to hear what stands out. Your double bracket bug makes me think of the weirdest escape sequence interpretation problem I ever saw. In some project a long while back in order to get a backslash we had to write something like
"\\\\\\"
.