Self-studying databases and doubts on PhD
5 comments
You might find searching HN helpful, for instance, just a few hits from a basic keyword search on stories:
https://news.ycombinator.com/item?id=36504838
https://news.ycombinator.com/item?id=17212926
There's likely a lot more to be dug up with a less half-assed search.
https://news.ycombinator.com/item?id=36504838
https://news.ycombinator.com/item?id=17212926
There's likely a lot more to be dug up with a less half-assed search.
Check out:
- designing data intensive applications
https://www.oreilly.com/library/view/designing-data-intensiv...
- Database internals
https://www.oreilly.com/library/view/database-internals/9781...
https://www.oreilly.com/library/view/designing-data-intensiv...
- Database internals
https://www.oreilly.com/library/view/database-internals/9781...
I got started many years ago with "SQL For Dummies". It was actually a pretty great book for getting started. Then, go to sqlite.org, read every page on the site, including the file format, read posts on the forum, read the source code. You'll learn a lot, and by downloading sqlite and playing with it, you'll have your own personal db lab. The Python interface to sqlite is very easy to use IMO.
There is different cases regarding PhD subjects, and it vary depending on the country.
The normal two cases is doing a master, and by contacting professors you find opportunities and build with the help of the future PhD director the subject. Second case is there is an open position for a already existing subject.
In extremly rare cases, the subject is proposed by (brilliant) students to Prof.
but in all cases, you don't work alone and you stand on the shoulders of giants
The normal two cases is doing a master, and by contacting professors you find opportunities and build with the help of the future PhD director the subject. Second case is there is an open position for a already existing subject.
In extremly rare cases, the subject is proposed by (brilliant) students to Prof.
but in all cases, you don't work alone and you stand on the shoulders of giants
Check out the CMU (Carnegie Mellon University) Database Group channel on YouTube.
url: https://www.youtube.com/@CMUDatabaseGroup
All of your questions (and much more) will be answered!
All of your questions (and much more) will be answered!
- How exactly does an SQL engine organize the tables? What data structure does it use (trees? heaps?)? Does it change to a B-tree when the index is created? How does all of this work?
- What does it mean by an elastic database?
- Completely unrelated, but this is one thing I've been obsessed with recently: How does one choose what to work on in a PhD, especially in the database area? For example, I am interested in query optimization, but what should I research? How does one start? Also, I've seen some profiles of individuals who pursued a different domain for undergrad and master's but then went into a CS PhD. How can one do this? Basically, how do you look for a problem in something you're interested in, and how do you know that it can be solved?
Thank you all! Appreciate your time.