Bitstamp api python wrapped
I invite you to DevConf! I sent two talks for the CFP and both have been accepted. The first talk will be related to my growing in recent years interested in Machine Learning. The second talk will be about my other fascination. How computers actually work? One day of workshop and two days of three tracks talks for very affordable price. Hope to see you there! Then I started writing the logic I wanted. I made the function to accept only GET requests you can change it in function. Otherwise, I return I just struggled a lot with debugging.
You need to run the function and check for compilation errors or runtime errors. There was also some weird scoping behaviour, that forced me to declare the Airports array within the function. You can see the code below. And I got to play with Azure Functions a bit. If you want to read more about other types of F Azure Functions, Mathias Brandewinder wrote recently two posts about timer and queue triggered functions.
Tune in next week for another part. Also, check previous episodes. There are some awesome comments to this post that add a lot of value. Please check them below. I was planning to start furiously coding on my project for this second post and start building some web API with Phoenix.
Just a few things that I found interesting and worth noting. Right from the start, there are few differences here. First one is standard compare operator. Second, from my current understanding, is useful mostly for comparing if numbers are of the same type.
To explain, look at this example:. And as a strongly typed language, will not allow comparing values of two different types. Elixir is dynamically typed.
It means, that it will also infer types, but this will happen in the runtime and also will do casts for you. You can also notice that those languages use a different convention for comments. But if you want to refer to the current value of, i. F allows mutability, but it has to be openly declared, and then you need a different operator to change the value.
Mutability is mostly allowed for compatibility reasons with. In this part, F is for me clear winner. You cannot change value bind to a label. It is much less confusing and makes more readable code. List operations are generally very similar. What I found interesting in Elixir, you can match not only head and tail, like in F but several first elements: Updated the code sample.
Check out the comments for details. The classic approach to lists is that you usually iterate through them with for loop. You have to do it in a more functional way, i. In F for loops are a gateway drug to imperative programming: It makes code dirty and is excessive. In F , blocks of code are delimited by the level of whitespace, similar to Python. In Elixir, functions must be wrapped in Modules. On the other hand, Elixir allows you to do multilevel Modules, which may be convenient in some situations.
A bit about Elixir pattern matching was mentioned in the first paragraph. You can also pattern match on function parameters, like shown below in the second example.
And you can further simplify it with guards. In F it looks similar to the case statement in Elixir. You can also use guards with it and much more. The Same variable cannot have values of different types, and nulls are non-existent in this language. You could have something similar using discriminated unions. I prefer F way again. As mentioned in the beginning, I have mixed feelings. And I can imagine for a lot of folks coming from other languages it is. Big points for Elixir for that.
I also like F more for strong typing. F has an abundance of operators. Some of them are really crazy. Check this Microsoft document to see all of them. Quick guides on Elixir and F syntax. The second one comes from the excellent blog of Scott Wlaschin. If you want to dive into F more, I highly recommend it.
Hopefully, I will find time for that. This post was edited to fix inaccuracies that were pointed out in the comments. Thank you for kind, constructive and informative comments!
It was my first DevSum, and it was awesome. Conference had two days and four tracks. Everything conveniently located in central Stockholm at hotel Clarion Sign.
Very close to central station and places for evening activities. The atmosphere was very friendly. I met well known faces from speaker community and made some new friendships. It was most social conference I attended this year, very much similar to how DevDay feels. My talk went fairly well. It was another installment of the talk I did at Swettugg and LambdaDays. I had around 30 people on public and I hope they got interested by type providers.
Big thanks to Tibi and Cornerstone for this opportunity. Slides and code are on github. In last month or so I did three talks on F in Poland.
NET organized meetup with two talks. This was great opportunity for my employer tretton37 to get some more street cred in Poland, so we decided to sponsor some food and drinks. I did my already well known introduction talk to F. I had quite a big audience around people and they were very engaged. I enjoyed great question and feedback I got after the talk. I used the same slides and code as in Warsaw couple months before.
Next dey was a DevDay: There were a lot of semi-negative opinions on the Internet afterwards, which is very sad and unfair. Looks like DevDay became victim of its own success. Last year was fuckin awesome, and people had some overgrown expectations. Videos are already online and you can watch them on youtube. But the strongest point of DevDay for me is community impact. It made largely distributed Polish. NET scene more united. On Saturday evening I did a talk on Polish virtual conference dotnetconf.
From statistics I could see there were about 70 people watching it live. Feedback I got afterwards kind of matched my expectations — 24 positive, 16 neutral and 2 negative opinions. Again — same slides and code as in Warsaw. Then I noticed it fluctuates a lot despite a general upwards trend. Hmmm … if I just bought at the right moment and sold at a different right moment, I could make money fall out of the void! Obviously I suck at this …. A low frequency trading bot, that sounds like fun.
Marrying the strictest of languages with the messiest of resources — the internet … what could possibly go wrong? Before my bot can do any trading and intricate algorithmic trading , it needs to talk to the marketplace of choice. Writing a REST client in most languages is simple. In Haskell, well in Haskell figuring out how to do that took me all night, then a bit of the morning and finally a helpful tweet from a stranger to tell me just how I was misusing monads.
First of all, we are going to need a bunch of imports. I am not perfectly certain what the OverloadedStrings bit at the top does. Nope, needs to be a well defined bag of things. If I understand this correctly, those strange symbols are applicatives.
If all goes well.