devnull3
How does this affect fertility?
My experience with AWS is that the pricing for each service is reasonably well documented and the calculator does descent job. The problem starts when multiple combinations of services are used and it becomes harder to reason.
With the advent of cloud, cost-modelling becomes an essential skill (which can be learned). One needs to be clear about total work that gets done and "how" that work gets processed. This in turn should translate to relevant cost metric (e.g PUT requests/s for S3 or IOPS for DynamoDB, amount of data scanned for Athena, etc)
This needs to be evaluated for zero load, normal load, 5x load, 20x load, etc. Zero load gives what is dead weight cost of the system i.e cost incurred when no work is being done (e.g EC2, EBS volumes, etc)
I think in practice, S3 data is often indexed using other DBs e.g DynamoDB, Postgres, MySQL etc. Can't this index be used to enumerate all S3 URLs? I am off-course simplifying this a lot.
If execs and top leadership simply walked the talk it will do far greater good.
The lady in pink is monitoring to ensure "fair" evaluation .. lol.
Also at 02:52 the lady says "are you saying women's place is in the home?". This clearly not what Harry was saying but it was interpreted to the other extreme. Reminds me of today's situation.
I am not white. But hiring for the sake of diversity alone is not a step in right direction.
PS: I have kept the title same as the video's
Dirty Harry on feminism and women's quotas [video]
For a medium level leetcode problem here is the time split (for which 20 min are given typically):
1. 4 min => Read/interpret/parse the problem statement
2. 5 min => Formulate the solution.
3. 8 min => Actual code
4. 3 min => Edge cases/review
---------------------
Notes:
* #2 You should think of various algos, DS and lock on to a particular one. If you cannot improve upon the time complexity, you need to make a split decision to either 1) continue to think more or 2) choose the next best and move to #3
* All you can do is steal one min from other phases but at the cost of less time in that phase.
* Think aloud in #2, #3 & #4
* At times even less time is available in case follow-up questions are to be accounted for.
* Code structure & consistency is important. You will be penalized if you write big monoliths.
* Additional conditions when GTFO is triggered: ["Solved the problem in 23 min instead of 20", "Did not think about that 1 scenario even though you took care of most of the important ones", "Solved the DP problem in top-down instead of bottom-up.. loser"]
----------------------
Optimizations:
* #3 should be reduced as much as possible. Choose a lang, know its standard lib by heart. This gives more time for #2
* Think of edge cases while writing code in #3
* At #2 one, you should be able to describe a solution (in your mind) detailed enough to convert into a code e.g Do DFS. Keep a max_val variable. Update max_val on values from left & right sub-tree.
* Develop intuition of doing some #2 work while in #1
-------------------------
What actually happens (or should happen) when someone practices leetcode a lot?
1. Reduce #1 time.
2. #2 => Quick recall of high level patterns already encountered
3. Able to generate multiple solutions.
4. #3 => Translate that pattern as fast as possible. E.g. There is a standard template for BFS, DFS, two pointers, etc
--------------------------
So the entire prep can be divided into two parts:
1. How soon you can zero-in a solution and convert into an outline?
2. How fast you can vomit that into a code?
Once you are comfortable in writing any code fast, you do not have to code every problem in leetcode. I see a problem and only solve it in mind and then check whether the approach was ok or not. I know I can code it fast
Edit: So for me if I have solved 200-300 LC problems, what it really means is I have actually coded in like 40-50 and remaining are just mind puzzles. If I do daily 5 mind solves, I can easily cover 200 in 40 days. I finish this daily routine in 30-45 min. (Hey .. I said this is dystopian)
------------------------
High level view:
* Practice incrementally and not in 2-3 months sprint. Think of it as daily exercise.
* This is just the way it is. May be I will do my part to change the system from inside when I am in an influential position. If you are able to find companies which do not do this shit, really good for you.
* Know that as senior dev, the margin for error is even less. So more important to practice incrementally.
--------------------------
I do not approve of this. Its bad. I am just a guy dealing with the "system".
Sure it looks like a cheap PR thing but this definitely is a symptom of heated market for employees.
[1] https://www.business-standard.com/article/companies/this-ind...
I can imagine the struggles of the research. Does the thought "Damn! I should have chosen a different problem" cross your mind when researching (which leads to question #1)?
PS: I am just a graduate with no intention of doing PhD.
The issue with mathematical notation is more practical one. Most programmers do not deal with maths (and notation) on a daily basis. TLA+ is a tool. If the tool is encouraged to be used in the field by programmers to model their systems, then it should "adjust" to their needs.
This means:
1. Better Debug-ability
2. Easier syntax
3. Better error messages
(I do not know how to do these and do not want to sound it as trivial)
This is where I want to make a subtle point: It does not have to be on par with mainstream language. I am not saying it should be as easy as Python/Go/Java. Solving for some of the low-hanging fruits would have disproportionate improvement in usability.
(A lot of ppl find parsing C++ templates & Rust generics jarring, let alone mathematical notations)
Another example of tool: https://www.wolframalpha.com/
It has both natural language input and mathematical notation as well (you see these options right below the search bar)
Click on any of the examples: https://www.wolframalpha.com/examples/ They are self explanatory for most I assume.
Even a simple "ForAll" instead of the symbol "∀" goes a long way (in my book) https://reference.wolfram.com/language/ref/ForAll.html
Also, the wikipedia talks about his research contribution and it is highly impressive. He is one of the top mathematician in the world.
Example: Terence Tao attending university level math courses at age 9 [1]
This cannot be explained by any checklist or regimen.
My guess is that if syntax is improved, a lot of people will give it a shot.
I wonder if we counted how many people got common cold/flu before the pandemic that number would also be large.
That is why said that no matter who is at fault here, this act of public score keeping is still not ok.
The employees there apparently kept scores (on a white board?) to make her want to quit the job [1]
[1] https://twitter.com/ashleygjovik/status/1427351298920239106
No matter who is in the wrong here, this is some A-grade toxic shit. This is unacceptable even for kids let alone adults.
This is about what a country as a whole has done. This includes folks from both side of the political divide.
1. Ran away from AF without taking lot of ppl who helped them in last many years. (There are videos on net to see on this)
2. President says AF was never about nation building [1]. Then what was it about?
3. Dragged/nudged allies to pour their soldiers e.g UK.
4. Already knew many years ago that they have lost and yet they lingered on.
5. Installed Hamid Karzai/Ghani govt and then made a deal with Taliban (which were surrender talks)
6. Knew that Pakistan is playing double game and yet did nothing about it.
[1] https://asia.nikkei.com/Politics/International-relations/Afg...
May be with memory wipe of currently what you know and the way the world is
* Learning effort to Reward ratio is good. A substantial syntax is valid for all of the DBs that support SQL.
* Very easy to remember the syntax. I have not used SQL in a long time but I can still write one without much effort (including the nested queries)
* Pareto: About 70-80% of data retrieval use-cases are well covered in SQL syntax (or a combination of multiple queries like union, creating temp table, etc)
* Tooling: Free & commercial tools which connect to multiple data-sources and provide SQL e.g [1]
[1] https://www.jetbrains.com/datagrip/ (I am not associated with jetbrains)
I wonder if they have leetcode style interviews :)
I think it stems from the fact that software is "soft" i.e. highly malleable and flexible. This improves time-to-market considerably and there is an inherent expectation built-in to "move"/"execute" quickly.
This also creates problems. Now the same thing can be done in multiple ways. There is a "my-company" way of doing. There is "my-way" of doing. Throw in personal tastes, likes-dislikes for testing, syntax, editors to name a few. Over the time, people take on multiple identities (e.g. FAANG, language fraternities, clubs of certain technology, editor fraternities etc). These mix and match in at best interesting ways and at worst in toxic ways.
Not only correct solution but also generate alternatives to showcase what other things you know to get strong-hire.
Example:
This problem was asked in Google: https://leetcode.com/problems/cat-and-mouse/
It is actually based on a paper [1]. Plus it seems it is expected that one needs to know about 'alpha-beta' pruning algos for such problems.
If you solve this using dfs ... its basically gtfo
[1] https://www.semanticscholar.org/paper/Undirected-Cat-and-Mou...
But I get what you are saying though.
- Unknown
(I read this sometime back on HN and it stuck with me)