I have been reading about F-star from some of its paper and the F-star tutorial, but I find myself quite lost trying to understand its concepts. For example, dependently type, Dijkstra monads, etc.
What are the pre-requisites to properly understand and learn about F-star?
Any explanation of links to any resource will be helpful too.
You might find the following general resources helpful.
https://softwarefoundations.cis.upenn.edu/
https://www.springer.com/gp/book/9783540208549
http://adam.chlipala.net/cpdt/
None of these are particularly specific to F*, but some of the concepts you learn there will provide useful background.
If this has been asked before then I'm sorry.
I've been given this question and have been trying all weekend to figure it out. I've looked at multiple websites but none of them explain the process. It's really frustrating me. Can anyone help? So I've been given the first two pictures below. I'm just hoping someone could maybe explain this to me? I need to practice this for my exam!
I tried really hard to understand what exactly the geometrical interpretation of Least Square Approximation but am not able to. I even followed the link but couldn't get what he mean by column space or null space. If someone can provide information on the topic or can tell me where to find relevant information it will be helpful.
Thanks
A bit off topic, posting about pure mathematics, but a bit of googling yielded this:
http://math.mit.edu/linearalgebra/ila0403.pdf
It's by MIT, so it's reputable for sure.
somebody knows where can I find more examples like these ones
http://doc.trolltech.com/4.3/tutorial.html
I want to study qt, but I think that it is not helpful to read all classes from A to Z, need practice, thanks in advance for any help
My recommendation for next step is thinking of some small project you want to make and then looking up programs from http://doc.trolltech.com/4.5/examples.html and especially http://doc.trolltech.com/4.5/demos.html that demonstrates features you want. The demos are also a good way to learn good Qt usage and idioms, because they have a feeling of being more complete mini-programs.
Apparently since I don't have enough rep to paste in more than 1 link, we had to do it this way..
http://www.google.com/search?q=qt+tutorial
http://sector.ynet.sk/qt4-tutorial/my-first-qt-gui-application.html
http://www.digitalfanatics.org/projects/qt_tutorial/
http://www.youtube.com/watch?v=QLT7oEt6gLE
http://thelins.se/learnqt/category/tutorial/
I'm wondering building a website like StackOverFlow (approximately the same features using ASP.NET ) How much Work-power and time does it take in your opinion .
My boss has asked me to estimate for work-power , time , cost and suitable technologies .
I appreciate any direction .
I believe that the site would take plenty of time to implement. If I'd have to pull a guess of thin air I'd say somewhere between 800-1200 man hours.
Then comes the setting up servers, ensuring scalability, testing, fine-tuning algorithms.
So depending on how good you or your team is it could take anywhere up to a year to write something like this.
Disclaimer: I am just talking based on 10 years of experience with web-development. But I could be COMPLETELY wrong.
Buddy, there is a website similar to this called http://startups.com
You can probably ask this question there. Its specifically designed to answer questions like this. Whereas stackoverflow is intended for programmers and programming related questions. I see this question being asked here a bit isolated.
People come to this site and think wow stackoverflow this is an easy site to create.
I mean all it is is post a question then people submit an answer. I think that is a big misconception. Maybe just maybe the database is quite simple, a question has multiple answers and an answer has multiple comments associate with it. If you dig deep into it the questions and answers could actually be stored in the same table...with some indicator as to whether it is a question or an answer. But to answer your question, I don't think it is as simple as one might think. It's definitely not difficult in the logical sense (it's doable). What I am saying is it is more then a one week job :).
it is not that hard to do the site. the design is nice but simple. the engine isint THAT complicated (or so it looks). biggest problem is the load that falls on this site and the hard task of moderating/maintaining it. and the best part of it is the idea ;)
I think that the diffuclt of stackoverflow is to get community (very good quality community, not like yahoo answers).
Not only that, also use cases from stack overflow are pretty cool and adapt very well to get a good community.
About work-power a good skilled programmer could start it, if at full time like a month or less could do it. BUT! the programmer should have the idea,not a freelance or something like that, freelance or slave monkey coder could take a more time to do it.
But there are more problems, like money to invest at very begin of the app for example in hosting / server power costs.
Also stack overflow, could be compared to forums...its like a forum evoled or something similar.
Someone said that requires a lot of work power, I disagree if you start something to get the best scability,etcs (like project of big scale) you are going to death of that project.
Start something simple, very simple when there are scability problems start with that but no at begin!
Probably longer than you expect:
Code: It's Trivial (by Jeff Atwood)