feenk

@feenkcom

We make your systems explainable. We invented and we build | .

Vrijeme pridruživanja: rujan 2016.

Tweetovi

Blokirali ste korisnika/cu @feenkcom

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

  1. Prikvačeni tweet
    27. svi 2019.

    We create because we want to educate. We believe that a fundamentally new development experience can change how you feel and think about software. We think this is crucial but we also need your help. We need you to engage with us. Find us here:

    Poništi
  2. prije 18 sati

    Working on a set of interactive slides describing the property of the graphical stack.

    Poništi
  3. proslijedio/la je Tweet
    29. sij

    Today's featured thing is by Not necessarily science focused, but an FOSS amazing dev tool & environment that rethinks how you write code. Check out for some neat examples

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

    A fun bit from the graphical dungeons of : a tooltip is associated with an element, like a button. Any element can be transformed in various ways, like through rotation or zooming. Still, we want the tooltip to not take that transformation into account.

    Poništi
  5. proslijedio/la je Tweet
    27. sij

    Some lines of code have their own weather, and it is different at both ends!

    Poništi
  6. 27. sij

    It’s our responsibility as developers to capture relevant narratives about our system. E.g., here is a class comment relying on examples (tests that return objects) to document the usage of annulus in (yes, that’s an actual mathematical concept).

    Poništi
  7. proslijedio/la je Tweet
    26. sij

    If you are after optimizing development, look at how developers read, not write, code. Code reading is the single largest expense in software development, and very few even talk about it.

    Poništi
  8. proslijedio/la je Tweet
    25. sij
    Odgovor korisnicima

    Indeed, a custom syntax highlighter inserts explanation targets as we type. This is how it looks like. Notice how in the example we do not save the code. It happens live.

    Poništi
  9. 25. sij

    Textual explanations of code tend to be somewhat cumbersome as they often require the reader to jump between explanation and code. We think there are other things we can do with out attention. So, in we can now visually link explanations with various code pieces.

    Poništi
  10. 20. sij

    Investigating the performance of the graphics backend the way: with a custom treemap.

    Poništi
  11. 18. sij

    is developed following . Thus, also documents the method it enables. E.g., the picture below shows a treemap of its packages and classes, highlighting in blue the classes that define a custom view, and in green those that define an example.

    Poništi
  12. 17. sij

    We had an issue with the cursor being off sometimes in the text editor. So, we built a view that shows the available cursor positions for a given text. Some details here: with

    Poništi
  13. 16. sij

    Hello from . Based on (bindings for Pharo by ) and .

    Poništi
  14. 14. sij

    Working on the visual appearance of the main tab to communicate better that there are several kinds of entry points into . Tools like the playground are expected. However, equally interesting are the slideshows and documents that deliver live stories in the environment.

    Poništi
  15. 13. sij

    Working on displaying live documents with a document-icon-like frame drawn as a vectorial border. And, yes, we are having fun. You?

    Poništi
  16. 11. sij

    We can now work with directly from native windows, and we can spawn the classic Morphic World at any time. This might look trivial but it required deep surgery to make it work. In any case, this means we are now bootstrapped. And quite proud, too.

    Poništi
  17. 9. sij

    We had an issue with references to external resources: during development we rely on the sources, while a release relies on a specific directory. To debug the problem we extended the resources access abstraction with a dedicated view.

    Poništi
  18. 5. sij

    Once objects can be viewed in different ways, we can combine those views into larger narratives. For example, the Squarified Treemap by Bruls, and van Wijk offers a heuristics-based algorithm. To debug it we made it inspectable. And then we documented it. Live.

    Poništi
  19. 3. sij

    The I in stands for integrated. Here is an example what that could mean. We browse a folder and find a Zip with an XML inside. We view the contents in place with syntax highlighting. To search through it we use an XPath that yields a set of elements we can inspect.

    Poništi
  20. 2. sij

    Every aspect of our systems should be made explainable. Take a squarified treemap layout. An problem in the algorithm does not raise an exception, it merely produces a less square picture. To debug the algorithm, we made it remember the steps it took and visualize them.

    Poništi
  21. 13. pro 2019.

    In our industry, we got accustomed to our algorithms remaining hidden, impenetrable. Instead, we believe our systems should be explainable. Take Undo/Redo in a text editor: simply listing the operations with respect to the current state makes the mechanism explainable .

    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:

    ·