275 karma · joined July 17, 2017
First of all, he has this weird take at the very beginning
> Interesting fact 1: Atlassian is the only company that has words "sh*" and "f*" in their core values.
Those values are "Don't f* the customer" and "Open company no bulls**" (oh the irony). This 'take' immediately threw me off. Why would you even mention something this trivial? I'll give it a pass as his emotions were probably elevated.
> After being in the company for more than a year I had found that folks with children are less likely to get a promotion. I had no evidence, it was a feeling.
Most of the folks I've seen got promoted had children. Having no evidence to support your claim in an article like this (with a banger title) is a red flag to me.
PTO is unfortunately something that I'm unfamiliar with. The country that I live in prohibits unlimited PTO by law, so I've never had that experience. Although, using the PTO that I acquire is still subject to approval of my manager. That part of the story is what the author should have really focused on. Going after the whole company in such a vicious manner is not a good look in my opinion.
I agree with most of the top comments here. Stay low, get a lawyer, deal with this silently. Hope his wife has a fast and easy recovery. Tough times, tough challenges for the author personally. No matter how hard I try, I certainly wouldn't be able to fully empathize with him.
Although his intentions were unclear by his vague approach to the subject, I believe he didn't mean to say women can't be engineers.
Most of the time he gave population-based examples of how women decided not to be engineers. His thesis was to show that forcing women in STEM fields is not a fair practice to both women and men who want to be STEM professionals.
Considering that Mozilla is already protecting their users from specific target sites, it is only logical to assume that they are also improving user experience for a website which has 1B+ users.
Edit: I still cannot overcome the fact that both products are owned by the same company.
5 or 6 years ago, our ex-minister, claimed that it is dangerous to work with computers since they can be challenging for the mind in a conference about cloud computing. Let that sink in.
I cannot think of a single positive reason behind this decision in 2020. All I can think of is that the people that came to this conclusion are the ones who graduated from Computer Science related studies in ~1998-2004~ and immediately got themselves in politics. I lost count of how many times have I heard that if you pay for it, it's just better...
Finally, I admit that I'm definitely highly biassed when it comes to Turkish Politics.
Blockchain has already surpassed its boundaries for multiple reasons. However, voting should be beyond that line. There are many questions that need to be answered before even thinking about using blockchain for voting.
- How will identification work?
- What is the proof-of-work scheme?
- How can you be sure that every vote ends up in the ledger? Transactions usually get lost and sometimes takes few tries to reach to miner.
- Most important property is that not a single vote should be traced back to its caster. Blockchain is all public, how are you going to anonymize everything? IP addresses of transaction owners are already open.
Edit: Formatting.
Now, I will list the problems we have encountered along the way.
First, you need problem suppliers. Blockchain does not need a problem supplier, hash puzzle is adjustable.
Second, proof-of-whatever must be very easy to verify. I mean the ratio between solving proof-of-whatever and verifying it must be really high. Unfortunately, read mapping is not a problem like that. Yes it is still NPC but verification takes way longer time than what is required.
Finally, privacy concerns. You must use encrypted, anonymized and distributed data. Current read mapping techniques do not accommodate to such needs. There are proposals[1] to satisfy these requirements but they do focus on hybrid cloud techniques which means network bandwidth is not a concern for them. However, blockchain applications are greatly concerned with network bandwidth.
*edit: references
They also add that Secret Chats in Messenger, Whatsapp and Instagram already support removing an already sent message. Facebook decided to also offer this feature for regular Messenger chats.
I guess any headline carrying Facebook, Zuckerberg and privacy concerns can make it to top these days. Modern online journalism is a whole another subject.
I had been all in favor of blockchain and cryptocurrencies for a decentralized approach to local applications, closed markets. To be fair, I never believed blockchain could reach global scalability and there are still concerns on that part.
We all saw the future value and possibilities before everybody started branding their deficient products with blockchain. I hope the bad taste surrounding this technology will wither in a short amount of time.
I think one can maintain code readability in a python implementation but documentation is the key here. Developer needs to clearly state the objective of each function.
For ethereum, you need one external element called: Ethereum Virtual Machine. Smart Contracts are basically byte code that runs on EVM. Without it, blockchain cannot function. So, ethereum development may require extra knowledge on top of blockchain technology.
After that, I decided to re-implement everything from scratch. My foremost constraint was to write readable code so that anyone could read the codebase and have an idea of how blockchain works.
My current draft of implementation can be found on https://github.com/halilozercan/halocoin , which currently lacks detailed README and documentation. However, you can still experiment with it by using API or CLI. I'm running a dedicated server to have an always online peer you can connect to.
[0]: https://github.com/zack-bitcoin/basiccoin
Edit: a word
Personally I met with python thanks to course assignments. It helped me to finish my projects way faster than any other language. I loved its simplicity and now even in my complex projects, I tend to solve my problems in "python way".
Also modularity, almost non-existent boiler-plate code, etc kind of things attract data scientists without computer science background.
However, when you start to think about it, nihilist thoughts start to kick in.