Έχουν υποσχεθεί ότι το patch θα είναι included στην τρίτη δόση.

I wonder if it's worth asking r/LegalAdviceUK about this, or any options you may have?

Can't bar them, or can't enforce it?

I don't see how you can disagree with those points as you also mention that need to be handled?

What I said is that implementing an abstraction does not automatically mean that a local and remote datasource has similar or equivalent levels of complexity.

I think you are proving my point here. As you wrote, it's not JUST a function. It appears as a function to the caller but there are enough complexities that need to be covered when delivering a sane and functional product.

Regarding #5, this is about UX not tech. While from an engineering PoV you can mentally abstract it and call it async, a user is unlikely to be happy if they see a spinner for 30s/60s without knowing how and why. This is a problem that a local access generally does not have due to the transaction speed while also Devs generally don't see as we have high end connections/hardware.

An engineer should definitely be seeing more than a function call. If they don't they lack understanding of the E2E product.

I'll talk about client side as I think it can illustrate this better. While you can have a similar high level abstraction over (say) an HTTP source and a local storage source, they can only be considered similar if (this is by no means an exclusive list):

​

1. Errors are primarily considered non-recoverable (e.g. your auth token expired? don't implement a transparent renew flow / your 1GB file upload failed? don't implement any continuation or retry logic).
2. HTTP caching works as expected.
3. The HTTP part does not implement any dances (hit api1 -> get data for api2-> use that for api3) as that would really compound the previous points.
4. The API is versioned and there is an explicit contract that the returned data contract will never be changed for a given client version.
5. You REALLY do not care about UX - a network call can have wildly different latencies/ success rates depending on network condition and user behaviour (is the user switching between Cell/Wifi? is the user on top of a mountain? is the user next to a wifi hotspot? is the user on a metered/capped connection? Is the device actually online or just connected to a captive portal?)

Essentially unless you are working with very simple cases, even a simple oauth backed `GET` or `POST` comes with A LOT more baggage than an equivalent function call hitting a local DB.

So while, on paper, they would look the same (`datasource.getData()`), when implementing them one WILL take considerably more time to get properly implemented and tested E2E.

Oh yeah, definitely.

I've had the (dubious) pleasure of both working with some of them AND seeing their faces when they realised that their team is far more employable than them as people started jumping to better places/roles.

I mean, if someone tells you that the team is at risk and you decide to ostrich because "back in my day developers used to work 36 hours a day, without a spec, punching code in binary on using two naked wires, while being sustained by the manly and stern look of confused disapproval by the senior management AND still manage to deliver the intra-banking exchange underbudget and ahead of time" they definitely deserve what's coming. Or they REALLY need training - but that's not the team's problem.

Thankfully, as you mentioned, they are becoming rarer.

What is GDPR? (Especially if voiced by someone who just implemented/works on Analytics)

If your manager(s) do not understand that, then they are either inexperienced or they (probably) deserve what's coming...

Be very afraid if an old hand starts a negative sentence with "The team...". They may be voicing an opinion that others are not feeling comfortable to utter.

"The team no longer trusts you/X/Y/Z" "The team feels unappreciated" "The team morale us low" "The team is burned out"

Είναι αυτονόητο αλλά θα το πω: Τα ρούχα και τα παπούτσια που θα πάρετε ή που θα φοράτε φεύγοντας να μην έχουν ή είναι συνθετικά/νάιλον/πολυεστέρα.

Επίσης πάρτε κάτι σε μακρυμάνικο και κανονικό παντελόνι (που να καλύπτει όλο το πόδι).

Αν έχετε μάσκες N95 είναι πιο αποτελεσματικές για καπνό.

Edit: αν έχετε φακούς επαφής, καλλίτερα θα ήταν να φορέσετε γυαλιά φεύγοντας.

There are few extra things that you need to consider in this scenario.

What you are describing is a scenario where:

1. You have limited information about privacy-related technologies
2. The information you have cannot be trusted as it cannot be freely verified
3. You believe that the nation is blocking access to information and/or is invading you privacy and you are actually bothered about this
4. The nation has more information than you
5. The nation has the means to keep information from you
6. The nation has the ability to edit information you receive
7. It is in the nation's interests to restrict access to privacy-related tools and knowledge
8. It is in the nation's interests to reduce the number of people with access to these technologies
9. The nation possibly has the ability to monitor and shape internet traffic

Based on the above:

1. If the nation you live in is so strict, how did you become aware of these tools? Are you sure these tools actually exist? - How can you know if say "Tor" or "Bor" is an actual tool and not a rumour or something in the grapevine?
2. Is your source reliable? Do they know what they are talking about? How do they know? Who told them? Is there any chance they are being played? Is there any chance they are trying to trap you? - If you have limited information it is very easy to be fooled as you don't have any way to know any better.
3. Now that you are aware, how confident can you reasonably be that you know how to use the tools properly and understand their limitations? - Would you be able to know if whatever tool you have is outdated or obsolete or if it has a critical and exploitable vulnerability? Would you know what Tor can or cannot do?
4. Say that you received a copy of the tools, how can you validate their integrity and provenance? - You can't compare hashes as you won't be able to find them, and there is no way to know if what you have is an actual Tor browser or something compromised or completely custom. What if it's a honeypot?
5. All checks out and you are happy about what you have. Will you actually start using it? I mean you remember Bob who was dragged to prison the other week because he read that article about so-and-so given a nice job in that border town where no-one returns from everyone seems to retire happily.

T important thing to remember is that any knowledge you have will be limited and asymmetric. And you will probably be paranoid about what the state knows about your actions and does not.

Remember is that rules and laws around these things can be enforced much harder if you are a local. And nations like this work by enforcing the idea that they can know what you are doing at any given time.

It's probably all the fires that need to be rendered at the moment...

1. Spend some time catching up with current tech trends
2. Ask people in my personal social network if they know of any open positions
3. Reach out to a couple job agents I've used in the past and trust.
4. Update my linked in and enable notifications that I've done so that every job agent in my network gets the notification.
5. Get flooded by random phonecalls for random positions at random times and promise to myself that next time I will definitely get a different phone number for job searching.

Usually steps 1-3 are enough if you've built enough connections, but it's something you have to put effort towards.

Any chance that the freeholder is absent? If this is the case then you cannot assume that there is a building insurance in place.

That can complicate the insurance a bit as you'd want to insure the building then, or have some form of structure where YOU have insured your flat but you are also insured against the possibility that the other leaseholders haven't.

I had to go through this a few years back, but unfortunately i don't remember the exact specifics of the cover, but this was flagged during conveyance and a solution was reached.

You can also check the mortgage paperwork (if applicable) as it should have been a condition for the mortgage.

I could have phrased that bit better 🙂

There is definitely a market but before you jump think of the complexities (on the phone so this is a dump):

• Sales. Who will reach out to companies to get them to convert/ use your product.
• Forward/backward compatibility - once it's a service you can't easily change things.
• Scalability and SLAs - do you have enough money to scale and fix issues inside the SLA?
• Licensing, pricing and piracy prevention
• GDPR/ Privacy framework implications
• In the beginning how will you add potentially breaking features because your main client want them?
• Future Roadmap. Say that you found a niche, unless you evolve fast someone will eventually offer an alternative.

As someone already mentioned, this is no longer a development problem, it's now business.

Others have given great advice on how to get them going.

Once they are going though, in my experience, the important part to remember (and the hardest to do) is to let them make mistakes (within reason) - don't helicopter over them.

Let them try things, and give them the space to experiment a bit. This doesn't mean that you let them merge bad code, but the only way to learn, actually learn, when fresh out of school is to try and fail so you can see what works and what doesn't.

This is a balancing act of sorts(supervise and prompt, but don't railroad), but if you get it right they'll be able to process much faster.

If the battery is swelling you need to change it ASAP as it can become a fire hazard/ explode.

You should avoid charging your phone if your can.

I don't have a medical background, but I'd expect that the order of causation is important to establish before judging how easy this will be.

Is the YAP state relevant to promoting cancer growth, or turning certain sensitive cells cancerous? Or the cancer itself requires a specific YAP state for its continuous existence? Or both?

If specific YAP states promote cancer growth then it may not be easy to fiddle with it as it may cause unidentifiable precancerous cells, cancerous. Unless there is a "safe" zone?

If it won't cause precancerous cells to turn, and there are not other complicated factors around the uses of the protein then it is starting to look promising.

As none of us have seen the code, I don't think anyone can objectively say that the are ripping you off, as this has to do a lot with how the existing analytics framework has been implemented/abstracted.

It could be a couple days/weeks (end-to-end) if nothing needs to be rewritten to a lot more if the current architecture will not support it. It also depends how large and/or fragile the codebase is as it affects how easy it is to refactor.

In any case, before you proceed you need to ask/establish the following:

• Is this a Time and Material contract or Fixed Price?
• What is the ETA?
• Does the quote include proper QA and validation?
• How many people will they assign for the job?
• Are they adding a warranty period?

Even if the bill is not broken down by time they still need to explain to you what service they are actually offering.

Agencies tend to add additional manpower to a project to increase the final cost, so the usual advice for when in doubt regarding a quoted price applies - always get multiple quotes.

The assumes that you have access AND the IP rights to the code. If not that is something you must definitely clarify and get as otherwise you are being locked in by the agency.

Going back to your actual question, it can probably be done cheaper - for comparison:

• £18K (+VAT) will get you a UK contractor at £400/day for 2 months, or ~1.5 months at £500.
• The same amount will get you an Easter European developer for a sizeable chunk of time.

You might like reading about a more ethically positive relocation:

https://en.wikipedia.org/wiki/Temple_of_Debod?wprov=sfla1

The moisture in the log turned into steam instantaneously due to the high temperature of the aluminium and as it expanded in volume it forcefully displaced the metal through the opening.

This article goes into detail:

https://hackaday.com/2020/12/30/water-and-molten-aluminium-is-a-dangerous-combination/

It's not about laziness - It's about time.

What's fairer? The person writing the library spends a couple of hours writing documentation on something they know about, or every consumer of the library spending time on something they don't know (and there is no documentation?).

Also, the whole point of a library is that (generally) you shouldn't need to know how it does things, only that it does and has well defined inputs and outputs. If I have to open isOnline to check, I'll either copy paste the code or just SO it.

At the end of the day not many people will take the risk to add an undocumented library in their (production) projects.

That may very well be true but people can't see it without documentation.

While you know what the libraries do because you wrote them and use them, you do have to explain exactly what the do to others. At the very least expected outcomes, side effects, expected exceptions and so on.

Not many people have the time and inclination to go poking into other people's code to see if something is useful or not. Especially if there is no clear and narrow scope for a library (which is fine, it just needs more effort in explaining why it's useful).

Have you checked if any other TLDs are available? For example `.io`?

That's how I went around my surname being claimed (and used) by a large firm.