Self portrait 01 big
Daniel Puglisi @daniel

Hi, I'm Daniel. I make Shimatta, Desk Hunt and cofounded Codegestalt. This is where I dump my brain.

This is a test post form the OS X app.

or Cancel

This is an excerpt of a conversation with @sirupsen

Regarding merging commonplace book and daily blogging: I’m thinking it’ll come down to a good search feature. At the moment you just have one feed and tags are basically the only thing to categorize your posts/thoughts with. A search which finds posts not just based on matching keywords but also on recognizing relevance based on the content of a post might be quite helpful in that matter. That’s what mostly bothered me with Evernote and sometimes caused me not finding relevant notes again because I messed up or forgot the keywords.

or Cancel

I'm currently working on cleaning up the backend of Shimatta and rearranging some things for future updates regarding private posts. More soon.

or Cancel

Chapter 2 (The Future of the Human Machine) notes:

  • cancer treatment will change in the next 10-40 years. Instead of chemotherapy we will use designer drugs developed with the help of genomics to melt cancer away.
  • PGDx develops a sequencing machine that crunches your DNA into gigabytes of data, parses out where proteins mutating and makes sense of why your cancer is growing. It gives you more information about your cancer than any oncologist.
  • sequencing the base pair in human DNA will be available for everyone in about 20 years. Current price tag is 1000$ per test. But not scalable for millions of people.
  • genomics can lead to designer babies. You can tell which diseases you're predisposed to, how tall/heavy you will be, skilled in math, what sports you will be good at, hair/eye color, hair type, when you will lose your hair, etc.
  • Craig Venter started Synthetic Genomics where they develop and grow human compatible organs on pigs. His second company Human Longevity Inc. aims to prevent aging.
  • Six of seven billion people have a mobile phone (more than have access to toilets) --> can provide innovation for almost everyone through this channel
or Cancel

Just read the first chapter of The Industries of the Future by Alec Ross. It describes how robots and automatization will probably steal human jobs. For example jobs like taxi driving (or even driving for Uber, think driverless Uber cabs), waitering in a restaurant, caring for the eldery and many more. Most of these jobs have a pretty high employment rate and are even under the top 10 of the most common jobs. What happens if all or most of those people lose their jobs? In the book Alec speaks about educating and reemerging them into a new job. But will there be enough jobs left? Of course with new industries new jobs are created. But won't those jobs require more specialized knowledge? And aren't more specialized jobs even rarer?

or Cancel

Here are some things that are in the pipeline for Shimatta:

  • Private posts
  • Auto linking @username (but only the ones that exist)
  • Shimatta API (closed for now)
  • OS X app for faster posting (that's why @rodrigo's feed is full with OS X and iOS development stuff)
  • Referencing other notes
  • Auto expanding content from external links (I'll probably create another service for this with a public API)
  • Emoji support :+1:
or Cancel

Ok. #tags auto linking is now live. #tags within the post are only used for referencing and do not tag the post itself. This might lead to confusion in the future. Will definitely keep an eye on this in terms of usability.

One reason for this is that we don't want users to spam #tags at the end of a post. That's why we limited tag usage to three. Another reason is if I want this post to show up under /daniel/tags/Shimatta I would have to explicitly add a #Shimatta tag. What if that word doesn't even appear in the content of the post? Having a separate tags field gets rid of artificially adding #tags and makes categorizing posts and the content itself a lot cleaner.

or Cancel

Just finished the second episode of Chef's Table. Great documentary so far. At the end of the episode Dan Barber draws the conclusion that the innovation of food doesn't happen alone with the views of a nutritionist, an agriculture economist or an ecologist. They happen on the plate where everything comes together.

This reminded me of the book Where Good Ideas Come From by Steven Johnson. One part of the book explains that the more people with different background knowledge get together to solve a problem, the more ideas and possible outcomes are generated as when you just try to solve it on your own.

What Dan tries to say is that those people need to start working together instead of going their separate ways. Because through the process of exchanging ideas can emerge something more beautiful than there currently is.

or Cancel

An update to the referencing posts feature:

Actually the timestamp URL could be used. The question is how do you reference other posts? I was thinking that you somehow use the unique ID of a post (e.g. post:3041). But wouldn't that be too complicated? Why not just enter the link to another post and let the parsing of the content take care of the rest. But then again, the timestamp URL maybe not be the best solution. Because what if in the future your are able to move a post from your personal feed to another? The timestamp URL had no chance to stay linked with the new location. With the ID URL it would still work.

or Cancel

I want to add support for referencing posts in the future. Similar to how commits can be referenced on GitHub with its SHA id. The old slug was a combination of the feed slug and the posts timestamp. This wouldn't allow for referencing posts globally. I thought about adding a solution which generates a unique random string like this (inspired from here):

# NOTE: We hardcode this for better performance
chars = [
  "a", "b", "c", "d", "e", "f", "g", "h", "i", "j", "k", "l", "m", "n", "o", "p", "q", "r", "s", "t", "u", "v", "w", "x", "y", "z",
  "0", "1", "2", "3", "4", "5", "6", "7", "8", "9"
]
[].fill(0,7){chars.sample}.join

but in the end I think this would have been an overkill and we just settled for using the regular ID of a post.

or Cancel