72 karma · joined April 10, 2013
While there are a number of comments questioning the utility of doing so and comparing it to having notes in a file, the fact that this is stored in my memory reduces latency when thinking or writing code. I no longer have to look things up which really improves my flow. I see the difference whenever I work with an API I already know and one I'm relatively new to.
I find that when I have more information in my local storage (memory), I can make more creative associations among the data and come up with better solutions to problems.
This is a very useful product to have for the intended target audience.
From looking at the landing page, your target audience is developers who need to generate PDFs directly from a template.
This is only useful if they need PDFs in bulk, if not they can export to PDF.
While developers are a good target market, there is also the market of all people who need to generate PDF reports in bulk.
You could add a simple frontend allowing anyone to upload a template, with a spreadsheet containing the values to substitute. Think of the spreadsheet as the API parameters. Non-developers can easily use this interface and are very likely to find this service very useful. In addition, you can charge more since the interface will not require any dev skills to use.
The catch with this approach though, is that it might be harder to scale. When targeting enterprises a single sale gives you more revenue.
All the best!
When I find some time I'll pull out my code and start using either errgo or the SpaceMonkey version.
Technical debt in these scenarios is usually limited to a single paper cycle (or maybe 2). This is avoided with simple practices such as planning out your code with comments before writing it, not copy-pasting code into 3 or 4 places, etc. There isn't much overhead, but it saves a fair bit of time debugging issues caused by human error. It also ensures you write as little code as necessary for the problem at hand.
I completely agree that when it's just a single paper, there is not much need to ensure you have an elegant library which can be re-used.
The other extreme is software engineers who focus overly on the mechanics and always underestimate how much technical debt they can afford. This results in over architected systems which try to plan for all eventualities.
Two useful skills to have as a software engineer are to know when to stop writing code and when it's okay to write messy code. The latter being done with the knowledge of when or even if you'll have to clean it up later.
Thanks for posting this.
EDIT: typos
Here's a library I wrote for golang which wraps it all up in a convenient package:
I'd happily pay $4 a month / $30 a year. I really like the Chrome extension as well. Here are some of the features I'd thought of adding to my (now cancelled) project:
Being able to see the meaning and usages of a word with a hover of some sort. I find it annoying to keep clicking on the right hand side to pull up the definition. Additionally, a number of definitions are just not available.
Something I find myself doing a lot is selecting and trying to right click. The 8 word limit on phrases means I'm stuck with typing stuff into Google Translate. For longer sentences context gets lost and so the translations are not accurate.
Being able to collect personal word lists. This is great for learning which is my primary intended use.
Keep in mind that I'm a beginner and the requirements of someone at an intermediate level might be very different.
Hope this helps and I'm looking forward to using it even more!
Here's some feedback if you'd like it :)
I just subscribed to the $9.99 per year version. However, I was mentally preparing myself to pay more, since it was very useful. I would have liked to try it out for longer though. The most useful part of it were the multi-word/phrase translations and I could only try out a very small number before it popped up the "subscribe" notification.
So to sum up, I signed up because it was just $10 a year, but would have paid more if I'd gotten to try it out for a short while longer.
All the best!
I was on an H1B in the US and it would have taken me close to a decade to get permanent residence and start a company that I could work for. For some context, I'm an ex-Googler and I've been part of the founding team of a successful startup previously. Despite all the above it would have been difficult for me to found a startup in the US and work for it.
However, after a few months of applying to Germany I now have a registered GmbH, an approval for a Blue Card and I'm paying my bills through consulting. I should be able to start work on my startup in a short while once I have sufficient run-way to pay my own salary for a year or so.
I just signed a lease for office space yesterday and I'm looking forward to exploring the German startup scene.
Does this play well with existing JVM threading support? More specifically, if there is a call to a synchronized method inside of a fiber and another JVM thread has entered the monitor, will this block the entire fiber scheduling thread?
The reason I ask is I'd like something that plays well with legacy code.
Life can be beautiful, even if it is not always so.