There's another github link (https://github.com/oreilly-japan/deep-learning-from-scratch-...) with the code for all 60 steps, but not the explanatory text.
127 karma · joined July 25, 2011
There's another github link (https://github.com/oreilly-japan/deep-learning-from-scratch-...) with the code for all 60 steps, but not the explanatory text.
I think what I'm trying to understand is this: if I use EdgeDB in production, how often will I end up dropping down to the SQL level to debug things? If I'm trying to debug a slow query, can I do it at the EdgeDB level? Or will I have to open a PostgreSQL terminal, see how things are laid out there, run EXPLAINs, check the slow query log, and so on?
When I use ORMs, the answer to this is "pretty often". The ORM makes my application code cleaner, but I still need to have a complete understanding of the underlying SQL representation in order to ensure good performance and debug errors. I'm curious how that compares to using EdgeDB.
With SQL, I have a mental model of how things work under the hood. For instance, I think of each table as being stored separately on disk, containing "rows". And the rows are really just equally-sized data blocks that are laid out back to back. B+ trees, with leaf nodes that point to (or just are) the rows, are used for indexes.
When I'm designing SQL schemas, I use this mental model to make guesses about performance. And when my queries are slow, I look at the execution plan.
My question is, how can I develop a similar intuition about EdgeDB? Under the hood, how are types and links stored in Postgres? And if I'm having performance issues, can I see an execution plan?
Otherwise, what you're saying would be true, and this could be easy to break/bypass.
They discuss the details of this in the paper: https://brave.com/wp-content/uploads/2021/06/sugarcoat-ccs-2...
With a traditional interview and job offer process, a new employee can ramp up without worrying their job is on the line. And I think this is important, because it can take awhile to ramp up to full productivity, which can be stressful if the new employee feels like they're being evaluated already.
Where I've worked, my new manager told me "Hey, welcome to the company. Please feel relaxed and take your time ramping up, you've already passed the interview and we're happy to have you here."
With your process, how do you deal with people getting stressed out during ramp up or feeling imposter syndrome?
If my down payment is 50,000, then in the rental (apartment) case I want to estimate how much I would be earning with 50,000 in the stock market.
[redacted]
However be careful when dropping out if you'll ever want to work outside the country. Most countries require a 4 year degree for work visas, and this can sometimes be onerous to get around. This is especially important for those who don't have US citizenship.
> Sorry, but anonymous users cannot vote.Please login or create an account here.
I know I selected python because it let me test my code by running it both before and after I submitted.
Anyway it's still really fun - keep up the good work!
I'm a CS student at the University of Waterloo, where most early CS courses and many advanced courses here use scheme. There are thousands of students taking CS courses here so in fact there is a generation of grads being produced where a significant number (thousands at least) of them base much of their CS knowledge on scheme. That makes it very relevant.
- the asteroid is 400 meters in size
- it's a "C-type" asteroid (http://en.wikipedia.org/wiki/C-type_asteroid)
The author presumes that everyone interested in coding should have a high level of confidence already. I disagree, and feel that if someone wants to learn about a subject, asking questions about that subject is exactly what they should be doing.
Chrome updates much more silently + in the background, which is one of the many reasons it's my favorite browser.
If code is written that satisfies these properties AND solves a problem efficiently, then it is elegant for being useful and easy to work with at the same time.
What's important is that you do it better than anyone else - so take a look at how they're doing it and figure out how you can do it better.