daanlo

In my recollection it wasn‘t about saving 10 cents in the beginning, but about saving 1-2$ per message, since one of the first use cases it enabled was free international texting. That was a HUGE benefit. All the first evangelists I knew were in long distance relationships ;)

It was pushed for mainly by his coalition partner (the green party) and none of them work for russian oil companies. Anti-nuclear is a very big movement in Germany and the majority of the population don‘t want to have them operated.

Quick update: I just sent a short & friendly email to my local member of parliament asking him about his position on the matter. Took about 10 minutes.

The easiest thing you can do is write a letter to your local member of parliament.

I don‘t know the proper solution, but building 27 ‚excellent clusters‘ for battery technology wouldn‘t make any sense. If it was national programmes then it would probably also be nationally funded and bigger economies (like Germany/Italy) would also have bigger budgets.

Thanks for the nudge! I was too lazy at the time and ranted here instead (which probably took longer than making the edit would have). I just edited the article and removed the questionable section with my edit. (And it was faster than writing my original comment - including the account creation process on wikipedia)

„Inductive reasoning aptitude is often counter-productive in fields like sales where tolerance is very important, because highly inductive people tend to be good at seeing faults in others.“ That is huge BS on very many levels. 1) Good sales is all about pattern recognition (e.g. in order to understand why someone wants to buy) 2) I wouldn‘t know why you need to be particularly tolerant as a sales person 3) In my experience „smart people“ see less faults in others / are more likely to understand where weaknesses come from. So saying if you are good at inductive reasoning = you are more judgmental is BS.

Founder from Berlin here. €50k for 25% is really off-market, even if you are a first time founder (at least in Berlin, Paris, London and hopefully all across Europe). And IMHO having worked in a startup (even if you aren‘t the founder) is seen as a BIG career plus if you join any corporate afterwards. I would say we have a thriving eco-system across Europe. Not at the level of SV, but still many big and meaningful companies with global foot prints being built every year.

The alcohol free wine is mainly nice to accompany lunch :)

We have alcohol free beer and wine in the office. Have been on a few 11am zoom calls with a big glass of beer in my hand - which was really nice (especially on a hot day with an ice cold non alc beer), but has sometimes confused the clients I was on a call with.

Imho, if above comment were a reason to be fired at intel, then it really wouldn‘t be an organization worth working for.

This very rare side effect, typically happens in the first 2-3 weeks after the vaccination. Src (in German): https://www.rki.de/DE/Content/Infekt/Impfen/Materialien/Down...

Symptoms of the thrombosis include: extreme headaches and/or bruises (without actually hurting yourself).

Src: my (potentially inaccurate) recollection of my doctor telling me about this.

Small observation on this great comment :)

I noticed on twitter that the culture (at least in my bubble) valued „smartness“ over empathy. In attempt to say something „smart“ it lead to many snarky responses.

I also noticed this pattern in myself, which is why I stopped replying to tweets. (It was easier for me to stop replying than stopping to reply in a snarky way).

For twitter I think this is not only a question of community, but also a question of design (ui/ux). And how the ui/ux shapes the community.

If I ran HN, I would consider if there are any (small) UX changes in the comment flow that could improve the „well, actually“/contrarian metric.

That is a really interesting thought. But isn‘t the chance of mutation per viral replication (which happens million-fold in each human per infection) and not per human? What I meant was that if we contain the virus to only ever get 1% of the population sick then there is a lower chance of mutation than if it gets 70% sick.

My layman understanding is that it doesn‘t work that way. Less spread = less chance of mutation = less chance of uber infectious new flu strain.

The three most common $reasons I see are: 1) They believe it will help them attract engineering talent, assuming many want to work in a micro services architecture. 2) They believe it will impress investors that they use micro services or be be a red flag to tell investors that their architecture is a monolith. 3) They believe their company will be HUGE one day and that it is therefore wise to prepare for scale now.

But as you can see in the comments in this thread. The coolness of micro services seems to be slowly fading. Feels a bit like the state of noSQL in 2014.

At least for Germany it seems fairly straight forward. You simply need to qualify for a blue card. https://service.berlin.de/dienstleistung/324659/en/

The target salary you need to achieve is € 44k / year.

As described in other comments, once you have found a job your employer will be able to help you take care of the admin topics of getting a visa.

There is no need to speak German and many Berlin based tech companies have English as the official office language (at least in the engineering teams)

Thank you. Very interesting read. I have never understood some of the low IFR estimates. If you look e.g. at numbers for New York State. They have had 50.905 covid related deaths (https://www.worldometers.info/coronavirus/country/us/) and roughly 20.000.000 inhabitants. That sets a pretty clear lower boundary on IFR of 0.0025. And clearly not everyone in New York State has had covid.

Imho that wouldn‘t cause quality to go up. It would just make it more expensive to develop and to fix bugs. Even more cover your ass would go on.

Or at least a huge share of that burden needs to be on the client so that they define and then test and control the SW they receive properly.

The problems with the software sound like typical big software project problems. Trying to cover a huge breadth of use cases with lots of very important tiny details and released in a big bang (one migration). It sounds like more of a project mgmt problem than a software problem to me.

But maybe I am just a hammer and see nails everywhere.

Imho this isn‘t all about the procurement process being broken. There must be something additinal broken that caused deloitte to fail at delivering this project.

Looks quite useful. I run a small agency and we frequently have the problem that we need a send from email for the project, but I don‘t want to setup gmail or something similar for our client. Atm we often use noreply@, but being able to give a proper email and also receive the typically very infrequent responses sounds great.

Software doesn‘t exist in a vacuum. The marketing team needs to know when the landing page / qr code (whatever) is implemented, because they need to plan their marketing budget. The customer care agent that gets shouted at because feature xyz is broken / not working as the customer expects, would like to give the customer an answer when it will be fixed. The customer care manager is also worried about her team members‘ retention.

So having a rough or concrete time line / roadmap is helpful for these parts of the business.

I also believe that a feature request is incomplete without an estimate. It is like a friend asking you to go buy him a car. What does he need a 3000$ subaru from 2003 or a 2021 Ferrari? Of course the friend can give you an insanely accurate list of specifications, but giving you a budget + some guidelines will probably be more effective for your friend and more fun for you. Especially considering that you know much more about cars (read software) than your friend. Knowing the budget you will be able to make much better choices.

If you take the allegory of a quote (which I think is correct) then you need to consider that the haggling process always also includes scope of the product. „I‘ll give you 5000$ for the car, but only if you include a free car wash“. And you can always use an estimate as defense against feature creep. „We are running low on budget, I suggest descoping xyz into the next iteration. Otherwise we won‘t be able to ship on time“. If on time is not defined then you can never have this conversation.

I assume by ISA they mean this: https://en.wikipedia.org/wiki/Income_share_agreement

I co-founded a home vertical farm company a few years ago (not in operation any more).

Plants grown closer to the person eating the food are way tastier. There are two main reasons: 1) as soon as you harvest, the plant is basically dead and starts losing nutrients and flavors. So avg. time from harvest to eating makes a huge difference for taste. 2) Since the transport is long, plants are often harvested when they aren't ripe yet. Again this leads to less nutrients and hence less flavor.

The unromantic truth is that plant growth is physics. They need water, nutrients and light and all of these can be administered in a "factory". The plant doesn't care whether the photons it receives come from the sun or a grow light, as long as the spectrum is the same. With modern grow lights you can mimic the environment you have in other parts of the world. E.g. you can have sun like in Sicily in Denmark.

The flavor will actually be better (as in MUCH better) and less transport means growers don't need to optimize for varieties that can survive a long transport.

We did a bit of work for laboratories this year and csv is not an uncommon exchange format between labs. In general almost all exchange formats are text based, with labs saying they will upgrade to „modern xml formats“ at some point in the future. So seen in this context a csv or an excel file doesn‘t really surprise me and should probably also be seen in this context.

It doesn‘t make Apple bad. It just means they inhibit innovation. The same way that a micro-managing manager that needs to sign-off on everything stops progress, but that doesn‘t make them a bad person. Your argument of porting everything to the web is absolutely valid. We are a small team though and having to rebuild everything for web meant we had to delay our launch - of course this is on us. Also some of our features don‘t work in web, since the native camera libraries are much better, but they aren‘t available on the web in sufficient quality (neither for ios nor android). And some camera functionalities are generally only available to safari on ios. It looks to me as if this is on apple, but may be a chrome/firefox issue.

Imho the app store clearly hinders innovation. In a recent project of ours (corona related) we had to wait over 1 month for Apple to approve our app - never knowing whether they would actually approve it. Google Play rejected it, saying it wouldn‘t allow any corona related apps from parties that are not government entities. As a response we ported everything to a web based solution. While I can understand their aim to keep scammers out (probably mainly to avoid PR issues) it was a real inhibitor to our legit project. For future projects I will always build web first. With the app store/ google play you are at the whim of some person at the other end of a textarea.

Interesting read and interesting conclusion: „We conclude that behavioural changes, temperature trends and school closure all contributed to the observed three-wave mortality patterns in the UK during the 1918 influenza pandemic, and that behavioural changes had the largest effect.“

I am not from the automotive industry, but if they are selling predominantly to automotive OEMs then I suppose Otonomo can be in serious trouble. Even a pending IP infringement case could potentially stop OEMs from working with them. Plus OEMs don't typically like companies that infringe IP, afaik.

This may sound overly harsh, but if you can't find 10 potential customers to ask them about whether they want your product: How will you find your first 10 real customers? It doesn't mean this is not a good product for someone to build, but it means this is a company YOU probably wouldn't be able to make successful. This is just from my experience, cause I have fallen into this trap in the past. ;)