Colleague I'm not too bothered about - I wish I was better equiped to address the attempts to bring me towards "Hitler was ok" but this is a person I can walk away from. And that I'm unlikely to change.
And workwise, I need to be be assertive, but I think I'll always lose to the argument with this owner - facts be damned. And those higher up the food chain seem unwilling to say no.... This is a situation and behaviour I have little control over.
But my room-mate I upset. She's a good friend and I have no wish to reduce or demean her. The last thing on a trying day and I failed either to identify with her concerns or find a way to get her (or myself) to think about them. I just went off on one.
I am more than happy to pay for a subscription to Whatsapp. I have a scattered family and it's a great way for us to stay in touch. As one of the more technically-minded family members, switching to a different service does not bother me but we've got 3 generations on our Whatsapp family groups and its ease of use and familiarity gives it inertia.
Not bothered by the idea of a relatively affluent westerner (me) paying more than those in less well off parts - already do for a lot of goods and services.
Facebook's data hoover and business model aside, are subscriptions, in themselves, unworkable for Whatsapp?
As opposed to "Trust us, we're Google/Facebook/Doubleclick/etc"? Not arguing for government necessarily. Just wonder who or what else would be the honest booked?
I can see a use case in my current work. We're building a dashboard visualisation for our product.
I'm writing the REST API backend for it - and trying to make that API as easy to easy to use for the front end (inhouse customer) as I can. However, I'm finding that I'm writing a lot of endpoints that are variations on the same data.
We will circle around, identify the common patterns/variations and consolidate a bunch of the code. But something like this, that facilitates sorting, grouping and filtering on the front end, could be useful.
And now Ireland is experiencing a housing shortage, with rental prices soaring and house purchase prices heading in that direction.
Market failure, policy failure, awful planning.
Living here, it's hugely disheartening to see a similar pattern emerging so shortly after a massive crash.
I live in Cork, population ~200k. In 2012, I rented a 2 bed apartment in the city centre for €750 a month. Now, I would be lucky to get a decent 1 bed apartment for €1000. And because bank lending rules tightened after 2008, opportunities to purchase a house/apartment have narrowed. Therefore, those (and families in particular) who cannot purchase have been on the receiving end of the spiraling rents. It took the government till late 2016 to put the brakes on the rent increases by creating "rental pressure zones".
I used Kirby for a travel blog a year ago. I needed something lightweight, for which I could prepare material offline and then upload when I had connectivity. Android phone + bluetooth keyboard were the preparation tools.
Using Kirby was an enjoyable experience. Easy to setup, good docs. Easy to work with on the road. A copy of the blog on the phone and on a thumb drive.
I can't offer a comparison with other file-based cms. Didn't look around. Though I don't doubt there are other very capable offerings out there. Tried Kirby, found it to be a low fuss solution that met my needs and didn't mind paying the few quid to continue using it.
There are libraries that allow C programs and Java programs to interact with Erlang as though they were Erlang processes. From the Erlang Interoperability guide: http://erlang.org/doc/tutorial/overview.html#id61008
Any recommendations for an open-source Java codebase to read that makes good use of the Java 8 concurrency features? Currently in a new job and struggling with an undocumented, uncommented codebase containing streams, rxjava, executors and futures. Could do with a different, hopefully documented, take on Java concurrency.
Similar experiences for me. Needed to spend time tweaking a wsdl so it produced the same behaviour in 2 SOAP webservice endpoints, one using dotNET tooling and the other Java. Worked fine after a bit of fiddling but leaves an uneasy feeling.
Long day, so will sleep on it before doing so.
Quite saddened by the day though.