I guess if both have the pixel buds then you don't necessarily need the phone?
I get that its not quite the smooth experience (yet?) that we want it to be but that we're approaching this previously unbelievable futuristic thing is amazing to me!
Smart Reporting is one of the world’s top startups in digital health. Our mission is to enable AI assisted diagnostics for the benefit of doctors and patients around the world. Already today, our award-winning software is used by thousands of doctors and institutions, including some of the world’s leading experts in radiology.
As a Senior Software Engineer, you will be an essential part of the rapidly growing development team at Smart Reporting. You will bring your entire experience to bear as we strive to build a high performance, high quality cloud-based medical product for AI driven precision medicine.
Smart Reporting is one of the world’s top startups in digital health. Our mission is to enable AI assisted diagnostics for the benefit of doctors and patients around the world. Already today, our award-winning software is used by thousands of doctors and institutions, including some of the world’s leading experts in radiology.
As a Senior React Developer, you will be an essential part of the rapidly growing development team at Smart Reporting. You will bring your entire experience to bear as we strive to build a high performance, high quality cloud-based medical product for AI driven precision medicine.
Smart Reporting is one of the world’s top startups in digital health. Our mission is to enable AI assisted diagnostics for the benefit of doctors and patients around the world. Already today, our award-winning software is used by thousands of doctors and institutions, including some of the world’s leading experts in radiology.
As a Senior React Developer, you will be an essential part of the rapidly growing development team at Smart Reporting. You will bring your entire experience to bear as we strive to build a high performance, high quality cloud-based medical product for AI driven precision medicine.
Smart Reporting is one of the world’s top startups in digital health. Our mission is to enable AI assisted diagnostics for the benefit of doctors and patients around the world. Already today, our award-winning software is used by thousands of doctors and institutions, including some of the world’s leading experts in radiology.
As a Senior Fullstack Developer, you will be an essential part of the rapidly growing development team at Smart Reporting. You will bring your entire experience to bear as we strive to build a high performance, high quality cloud-based medical product for AI driven precision medicine.
Smart Reporting is one of the world’s top startups in digital health. Our mission is to enable AI assisted diagnostics for the benefit of doctors and patients around the world. Already today, our award-winning software is used by thousands of doctors and institutions, including some of the world’s leading experts in radiology.
As a Senior Fullstack Developer, you will be an essential part of the rapidly growing development team at Smart Reporting. You will bring your entire experience to bear as we strive to build a high performance, high quality cloud-based medical product for AI driven precision medicine.
I second this. I used to think practicing gratitude was stupid, or at least not really worth my time. I have recently picked up stoicism and one key techniques seems to be "practicing negative visualization" - basically imagining how much worse of you could be. I found that once I really think through all the hardships that I could find myself in I appreciate my current situation much more and feel much happier.
Curiously, I think I also get more done now because I feel better, am in a better mood and spend less time anguishing about all the things which are not perfect or could somehow be better. It has also made me aware that many people do find themselves in various hardships and my appreciation for my situation has really grown again through this.
Stop being so hard on yourself and cut yourself some slack - if you're the perfectionist type (like me) it does a lot more harm than good!
If someone is wondering about the relationship between sum types (discriminated unions / case classes) and the visitor pattern, I've written about this here [1].
But in the end I think for most people 'understanding' the concept of monads is just something that is not to be had within a couple of hours. It takes a little bit of patience thinking about them and using them for a while.
So the obvious question: What did you focus on that let you improve way more than other people? I do write code and learn something new every day and while I would say that I have improved a lot in the last few years I am still ways away of where I would like to be. Somehow I have the feeling this is not going to change.
I imagine that everyone has to decide specifically where they want to improve and figure out how to work precisely on that, but I would be interested to hear what exactly has worked for you?
Has it been decided yet if garbage collection should be moved out of the core and only be provided as a library? If memory serves me right there was some discussion on this shortly after the 0.6 release [1][2].
Here is a simple suggestion to end the lawsuit madness: The loosing party must bear all costs of the process. This is how it works in Germany. Added benefit: The expected value for suing people over the most ridiculous things is suddenly negative.
Re 2: Well, sometimes you need them, but they do throw exceptions on empty lists, so if you don't know for sure that the list is non-empty it is definitely a bad idea to use them. I just thought a warning would be in order when presenting them. This is a point where Haskell's type safety (can't know at compile time if a list is empty or not) falls short and I think a lot of Haskellers try to avoid such functions for this reason. For example the Xmonad code uses zippers in a few places instead of lists which always have one element.
There's a few more points that I can't go into in detail due to lack of time (reason for use of recursion instead of loops, if / case statements, purity) and I do appreciate the effort and can imagine that it will prove useful but I felt obliged to point out these things. If I can see them it's not a good sign ;)
I am afraid this is not a very good guide. I am by no means a Haskell expert, but even I can pick out a number of things which are not done very well and are not idiomatic Haskell. For example:
> myMap func [x] = [func x]
> myMap func (x:xs) = func x:(myMap func xs)
myMap does not deal with the empty list, will throw an exception if it is called with one, and there is no reason for it. (Just replace myMap func [x] = [func x] with myMap func [] = []).
Several functions that throw exceptions on empty lists (head, last) are introduced without any warning (such functions are considered bad style by many Haskellers).
> -- Haskell has a very strong type system, and everything has a type signature.
I believe a 'type signature' is the annotation, and no, not everything in Haskell has a type signature. Everything has a type.
> -- if statements
If is not a statement in Haskell, it is an expression. Same with case 'statements'.
Hi, I'm developer of this RSS reader and want to share with you why Haskell is a big win for my project.
First. Haskell is a fast compiled language. Most RSS readers are written in Python, Ruby or PHP. And they're all quite slow or requre a ton of servers to handle the load. With Haskell I'm able to quickly implement complex features and don't think much about performance.
Second. Haskell is very high level and handles concurrency well. It's not a problem to write very generic code or spawn thousands of threads.
Third. There a many good libraries now (much more than 10 years ago ;).
I want to thank Bryan O'Sullivan, Michael Snoyman and all other package authors for their efforts on making Haskell true platform.
I'm especially like text, riak, aeson, http-conduit and warp packages. They're used 24x7 under load and I haven't found any major problems with them.
And few quirks.
Unfortunately not all packages are equal in quality. Many libraries are toys or don't work well under load. But at least there are libraries to take some code from.
Bindings to C libraries (as well as C libs itself) are evil. I've had problems with almost every C package I've tried (curl, regex-pcre, hsdns).
Long-lived ByteStrings can cause memory fragmentation and ten-fold performance drops. So I'm using Text for everything except I/O.
Haskell was missing fast malformed html/xml parser. But it took only a couple of days to write fast-tagsoup package that parses tens of MB/sec.
In general with Haskell I can quickly write high level code that runs fast. And (at least for my project) I'm seeing that most tasks now are CPU bound (due to fast SSDs), not I/O. So compiled yet high-level languages shold gain more popularity now.
If you have some questions about reader implementation details feel free to ask me.
PS: reader is profitable, so I'm thinking it could be counted as a Haskell success story ;)