jevakallio

6 ms·

1.
by jevakallio 9mo ago
Marker | Product Engineer + Full Stack Engineer | Onsite/Hybrid, London, UK | Full-time | https://marker.page/jobs | £100K - £170K + equity Marker is an AI-native Word Processor – a reimagining of Google Docs and Micro
2.
by jevakallio 1y ago
Marker | Product Engineer + Full Stack Engineer | Onsite/Hybrid, London, UK | Full-time | https://writewithmarker.com/jobs | £100K - £170K + equity Marker is an AI-native Word Processor – a reimagining of Google Docs a
3.
Show HN: Communicate important updates to your team via Git commit messages(github.com)
9 points by jevakallio 6y ago|1 comments
4.
Show HN: A Jest Reporter to group, hide and prettify spammy console warnings(github.com)
10 points by jevakallio 6y ago|0 comments
5.
by jevakallio 6y ago
Foam author here. Yes it can. GitHub support is purely optional. I've improved the Getting Started guide to reflect this.
6.
by jevakallio 6y ago
Foam author here! Fiddly, yes. This is very early stage project and in need of polish. Lacking backlinks, however? We actually got those, thanks to the VS Code Markdown Notes extension: https://foambubble.github.io/foam&#x2F
7.
by jevakallio 6y ago
Amazing! Please let me know in GitHub issues or Twitter DMs how you get along. This is a very early alpha release, keen to hear feedback at all levels!
8.
by jevakallio 6y ago
Foam author here! I am very open to all suggestions in this area. Foam is a new project I built solely to my own requirements, but I'm actively seeking feedback on how to make it more broadly applicable as per our principles: https:&#
9.
by jevakallio 6y ago
Foam author here! I'm not personally familiar with VSCodium, but contributions in this area would be extremely welcome as long as they don't prevent any of our Roadmap features working on VS Code! Check out the contribution guide
10.
by jevakallio 6y ago
Foam author here! I also don't like dependency on Jekyll, and over time I want to build a bespoke static site generator for Foam (possibly based on Gatsby) that's able to create a richer browsing experience. Thanks for the idea! I
11.
by jevakallio 6y ago
Hi! Foam author here. We generate markdown references to bridge [[wiki-link]]s to work with Markdown tools. For the time being this is optimised for a) the editing experience in VS Code and b) the GitHub pages publishing pipeline, so it&#x2
12.
by jevakallio 7y ago
Yes.
13.
by jevakallio 7y ago
That's actually a good idea. Right now we pay the salary to you, and you can then donate it to a charity. It would be way more tax efficient to just skip the middle step. Will take this under consideration!
14.
by jevakallio 7y ago
I guess they'll have to work overtime to process all the applications ;)
15.
by jevakallio 7y ago
I agree this could be the case, except that there is no pressure to work on anything work-related. You can literally contribute to any OSS project, whether it's your own video game side hustle, a learning project in a language we don&#
16.
by jevakallio 7y ago
This is a great idea. I don't know if it's even a starter, tax code wise, but would be amazing if it could be done. For the time being, we are happy with $20 for the reasons outlined in the post itself. It's not an incentive,
17.
by jevakallio 7y ago
It's set at 30 hours a month. This is not for budget reasons, only to discourage excess working off-hours. This adds up to about a workday per week, which is what we feel is reasonable.
18.
by jevakallio 7y ago
Author of the post here. Realistically, we can't pay people full engineering salaries to do random OSS. Our team can already contribute to OSS on their work time when it relates to their work, or our own projects, but for the personal
19.
Paying for Open Source Contributions(formidable.com)
316 points by jevakallio 7y ago|132 comments
20.
by jevakallio 9y ago
I love the annotated source code, but I wouldn't necessarily recommend the Underscore library code itself as learning material to budding developers - it's optimised for size and performance, not legibility and idiomatic style. I
21.
by jevakallio 9y ago
It's written with Docco, a tool created by Jeremy Ashkenas. It's used in docs of his other projects, such as CoffeeScript and Backbone, too. http://ashkenas.com/docco/
22.
by jevakallio 9y ago
Hi! I'm the author of the library, and just wanted to say that you are absolutely correct about Redux Offline not being a suitable solution for weeks of active offline use :) Regarding the "get a connection within one hour",
23.
Show HN: Redux Offline – Offline-First Architecture for Web and React Native(medium.com)
1 points by jevakallio 9y ago|0 comments
24.
by jevakallio 10y ago
Correction to the previous: The CycleConf changes are now part of the official cycle-react-native repo: https://github.com/cyclejs/cycle-react-native
25.
by jevakallio 10y ago
We looked at Fastlane and thought it looks very interesting, but because we didn't have personal experience with it, we decided to go with what we know: Bitrise for the CI, CodePush for the app live updates. We would love see contribut
26.
by jevakallio 10y ago
Please take a look and let us know if you run into issues! We've just launched Pepperoni, and it's not yet as polished as we want it to be, but we'll be there soon. For comparison's sake, check out https://git
27.
by jevakallio 10y ago
Haha, I work at Futurice, and I wish I knew the answer to that question :) Here in the UK it rhymes with Avarice. In Finland it's more like Future Rice.
28.
by jevakallio 10y ago
Great question! We are investigating adding Relay support, as well as a PostGraphQL endpoint (Postgres+GraphQL) to the soon upcoming Pepperoni Backend Kit. Right now we've included what we know works well, and we don't yet have ex
29.
by jevakallio 10y ago
Thanks for your interest! It's definitely more of a project boilerplate. We have big ideas for the future, but starting out small. Thanks for the notes on the mixed messaging, we'll tweak the website to be more informative.
30.
by jevakallio 10y ago
Thanks for the feedback! One of our team members is working on a sample app, launching as soon as it's done :) We didn't want to delay the release until "everything" was complete, in order to gather input such as yours.

More ›