It's not about the Wework product "office space" being fraud, but about the product "wework shares" being sold as a good investment which is questionable
Additionally you need to test it doesn't trigger a positive when someone had a cinnamon flavored mint before. Or a citrus one. Or ate a mushroom sandwich. Or has diabetes..etc etc
Dunno.
I am bootstrapping as single founder and the investment was basically
- 2 days to change the app code so only data necessary for the actual use case of the app is processed and stored
- 1 day to formulate a GDPR privacy policy in my own words (what data is captured, how is it used, how is it stored, etc)
Unless your business is somehow is fundamentally at odds with GDPR (flashlight app to grab IDFAs and sell those) it doesn't really seem terrible. Especially so as it is in my own interest even without GDPR to minimize my risk surface in case I get hacked and user data is leaked.
It would not be about detecting the change of hands but about detecting the (malicious) monetization.
Depending on the type of extension this might still be hard to do, but I could well imagine heuristics triggering a manual check from the extension store providers.
For Electron signing we use Tucows Code signing certs (you need to register as Tucows auther for free) which are provided by Comodo for $140 for 2 years.
Didn't have any issues besides getting a proper CI/CD process running.
Huawei P10 lite.
If that should be the explanation I would actually be relieved - as said, it didn't fit my mental model they wouldn't have a super slick app with so many Dev resources.
Nice article.
The amount of in-house procedures/tooling developed by the backend seems impressive (maybe some not invented here syndrome but can't judge really).
What I am astonished at though, is that the backend part of Über seems so professional while the Uber Android app feels like it's build by 2 junior outsourced devs. Have rarely used an app which felt so buggy and awkward. (aside from regular crashes, e.g. when registering for Jump-bikes in Germany inside the app, I had to restart the app to have the corresponding menue item appear).
A domain goes through various stages before it becomes available for registration again. They are auctioning them after expiration but before general availability.
Something like "[myarea] open locked door" can have Google ad bids in the range of 30$,so there may be money in there for Google not caring for quality organic results
If you have a company of 5k plus employees different teams are bound to use different cloud providers without even being aware of such.
Such companies are also those being interviewed by Gartner or Forrester etc.
Seeing that electron application code can easily be inspected inside the asar container (I.e. you can't trust the client) :
How would you approach the problem to encrypt secrets locally? The only approach I could come up with involves receiving a symmetric key from a server with certificate pinning, but even that seems quite insecure).
This would definitely be illegal in Germany where I work as CTO.
Even having employees sign some letter of acceptance of such would still be illegal as a court would assume an employee was in an uneven power position and therefore not able to refuse even if they wanted to.
If this is a small company, I would probably not worry too much about process and ask the concerned employee to discuss this in a friendly and open way.
Maybe a misunderstanding which can be cleared, maybe the reason is actually lying deeper. Good chance you can resolve this by being emphatic and act understandingly.
That being said, I would note down a memory protocol afterwards in case this turns ugly after all.
One aspect I didn't see mentioned here so far which explains these mechanics beyond simple "the government is just incompetent" rethoric:
Unlike some (but not all) private institutions, regional and national government officials are incentivized to downplay the budget/runtime of major infrastructure projects as
1) the person is often not going to be around and accountable anymore once the true extend comes to light
2) telling the truth/adding proper buffers would make the project not being accepted by voters. So downplaying is the only way to get such projects through at all in many cases
It gives uBlock Origin a score of 100 in the Screenshots, but does this actually translate to 100% performance compared to page load without extension?
Or just go with hooks.
Obviously there are quite a few pros and cons but for us the reduction in boilerplate led to a net increase in cognitive understandability of our code base so to say.
I would guess this is not just to protect user data from being scraped.
LinkedIn earns a lot of money from users paying for recruitment services (as in get advanced filters to search for candidates and to send them job proposals). This costs 4 figures per month.
So the LinkedIn product management has a high value from learning which extensions people are using to substitute or enhance their paid services even if the extensions don't violate the ToS.
For a b2c app usually it is neither server cost nor Dev time being the main cost drivers but cpi campaigns. So you should have a way lower profit margin here than someone just looking at tech expenses might intuitively expect.
I am VP engineering in a 100 person company with 30 engineers. Noone is asked to work more than 40 hours and <5% do actually work more.
I will happily have someone work 4 days 8 hours and 30% of our devs are in such a model.
But I would not go below this (especially not less than 4 days in the office). Devs aren't working in total isolation, but are heavily involved in their cross functional product teams. Reducing availability further has an above linear hit on team productivity as colleagues become more and more blocked in their own tasks.
So: just saying this is more complex than looking at increased per-hour productivity of a single person
From my experience you don't have fortune 500 companies as a customer as a >50person,>5mil revenue company.
You may have employees from such companies paying you via their business credit card, but will never get through real procurement without documented SLA procedures which are required to prevent a scenario exactly like this.
At least for us, most A/B/.. tests require a stable assignment of test to user as key metrics like retention would obviously skewed by randomly assigning on each visit/page view.
The article vaguely links Cambridge Analytics to GDPR. Is there really a connection or is the article merely trying to frame GDPR negatively by comparing?
I would rather interpret it such that the original department ordering the web page did not understand the business model of their overall company (with the GP having no chance to learn the real business mechanics from them) and that the real estate people actually saved the project in the end.
Wouldn't want to work there myself though ofc.
An interesting situation is when the app has cues to a user's current intent. In such cases it wouldn't want to totally rearrange the UI on the fly (move the food court) for the user as the user expects consistency (and the cue might be wrong). Maybe this is a case where contextual messaging makes sense.
The idea of "people won't buy things they can't judge by holding it in their hands" was still strong back then.
That's why Amazon was successful selling books where quality was trusted implicitly without that physical judgment being necessary.