HN user

wlk

86 karma

personal blog: http://wlangiewicz.com

Posts0
Comments48
View on HN
No posts found.

That's exactly one of my use cases, I have setup runner for 2 projects last week and action runtime went down by a large margin, from 10-15 to 3-4 minutes.

I use single dedicated server that costs ~40EUR/month, AX41-NVME, and each runner is a separate user account to allow for some isolation.

Depending on your setup, you might need to spent some time adjusting jobs to have proper setup/cleanup and isolation between them (but it's not really Hetzner specific, just general issue).

Probably not, my tip is to sign up, but then wait for the recording to be available (they usually are), once a recording is posted you can see where did they post it to and then download. I do this from time to time

When required people just omit the diacritic signs and replace the letter with regular ASCII letter, so for example: ż->z, ł-l, ó->o, etc.

When used in (computer) writing this is very readable, but no one would do this with handwriting, I think most common cases nowadays would be SMS messages (especially on dump phones) or some weird displays that are unable to properly render diacritic letters.

Some webmail clients (and potentially other web communicators like online chats - FB messenger, etc) might pre-fetch all URLs send in the email or chat.

The pre-fetching will use the user's context (and cookies) because it's executed by the user's web browser.

Location: Poland

Remote: Yes

Willing to relocate: Yes, only for short period of time

Technologies: Scala, Akka, JVM, Akka-http, Play Framework, Java, Linux, MySQL, MongoDB, Big Data (Hadoop, Spark, etc), Docker, Redis, AWS, RabbitMQ, Couchbase

Résumé/CV: https://www.linkedin.com/in/wlangiewicz

Email: wlangiewicz@gmail.com

Github: https://github.com/wlk

I'm looking for a full time remote position as a Software Engineer focusing on backend development in Scala

Location: Poland

Remote: Yes

Willing to relocate: No, but willing to visit the HQ for extended periods of time

Technologies: Scala, JVM, Akka, Play Framework, JavaScript, MySQL, Bitcoin

Résumé/CV: https://www.linkedin.com/in/wlangiewicz

github: https://github.com/wlk

Email: wlangiewicz at gmail.com

I have been working full time in Scala for over 18 months and would like to continue working in that area. I have been working remotely for over 4 years now. My previous experience includes Java, Hadoop (big data stack).

For private/small projects free BitBucket is enough. For larger projects I have used self-hosted Gitlab which was running very well on relatively low spec server.

Location: Poland

Remote: remote preferred

Willing to relocate: not really, possibly only within Europe

Technologies: Hadoop, Java, Android, Scala

Resume: linkedin.com/in/wlangiewicz

Email: wlangiewicz at gmail dot com (let me know that you are from HN)

I have been running 2 large Hadoop cluster, at the moment interested more in api/backend/server side development in Java/Scala, I'm also involved in local meetups, co-running Software Craftsmanship group, presenting at other meetups from time to time. I have been working remotely for a long time now, I'm especially interested in part-time offers (~20h/week)

I can address first of the issues you have mentioned: I have worked both in situations when whole company is working remotely or only one/two people of out dozen were.

In the second case, those people were very often left out of the most communication that was happening in the office, and for them it must have been not very good situation to be in. There was no general plan for handling this situation and trying to include them in meetings and decision making process.

But when whole company is working remotely, the situation is completely different, everyone is at the same level, and you really can make it work.

A lot of that, especially points 1-3 depend on if you work with other people synchronously or asynchronously. At my current job we all try to work as much synchronously as possible, so there is no real difference from any other "office job", except everyone is in different location (we all are in roughly the same timezone), and we don't have to commute. We focus on trying to keep sanity, and keep working hours (my experience is that it helps a lot when working remotely)

For shops that allow/ or just work asynchronously, other arrangements need to be made to allow that. Usually more and more stuff is written and stored, so everyone can join and leave any moment.

There is a similar book being worked on by other ruby-remote working company: Arkency, http://blog.arkency.com/2013/09/arkency-survival-guide-to-ef...