Re: [JOB] Looking a Clojure programmer
I suppose this is the correct domain: http://karriarforetagen.se/ On Thursday, December 31, 2015 at 2:04:39 PM UTC+1, Timo Sulg wrote: > > Hi, > > i'm a Clojure programmer in *‘Skillable’* - a Stockholm, Sweden based > startup building a tripadvisor.com > > for employers: employees rate own employers, we crunch the data for > companies ranking, matching and suggestion. > > > I joined Skillable exactly 1 year ago as full-stack Ruby developer to take > over mostly outsourced monolithic RoR app. > > After had encountered problems with scaling and fixing spaghetti code > during large-scale marketing campaigns, > > we decided to scrap old experiment by taking the idea that worked best and > start building a better product from there. > > > We've launched a simple MVP in partnership with karrierforetagen.se ( > http://review.karriarforetagen.se/?c=skillable) > > to award ‘the most exciting companies to work for in Sweden’. We’ve built > the ratings mechanism and the core API, > > which exposes all essential business logic behind it ( > https://api.skillable.com/index.html) – The API and all background > services are written in Clojure (compojure-api, fink-nottle, AWS, docker) > > > Currently we're building a more advanced product that'll show results of > reviews and recommends companies > > relevant to the visiting users. There's lot of work to be done in backend > – we need to add additional services, > > tweak search algorithms, experiment with recommender systems, collect > metrics, enrich data, > > contribute back to open-source libraries etc. > > > I'm flexible in how we're going to partner up, but you should be able to > visit our office at least for planning sessions. > > There's no formal hiring process, feel free to contact me on twitter/slack > (@timgluz) or send me old-school email (timo...@skillable.com > ). > > > Happy new year! > > Timo Sulg > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
A few fresh Clojure libs: authorization, multi-requests and more
After lurking around the Clojure community for well over a year now I thought it might be time for me to share some hacks I’ve made while working on a hobby project, so I pushed a few repos tonight. https://github.com/molst/annagreta - simplistic authorization https://github.com/molst/treq - simple multi-requests https://github.com/molst/pisto - speedy dev env helper (based on Stuart Sierra’s ideas) https://github.com/molst/hazel - Datomic helpers Would love to hear if you find any of it useful, Cheers! -- -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Minimizing the download of js code in Multipage ClojureScript webapp
Thanks for the tip, Mimmo! On Sunday, January 27, 2013 11:33:46 PM UTC+1, Mimmo Cosenza wrote: Hi Marcus, I found the same solution Evan suggested to you. You can read about it here. https://github.com/magomimmo/modern-cljs/blob/master/doc/tutorial-06.md and you can also define a single init function which is shared by each source cljs files by passing it the parameters you need to setup each html page differently. (A kind of abstraction to apply the DRY principle). Mimmo On Jan 27, 2013, at 10:03 PM, Marcus Holst holst@gmail.comjavascript: wrote: Thanks Evan! I actually already started along this big js blob path and was just beginning to see the problem with clashing page inits. Your solution with an init func per page will probably do just fine for me too so I'll try that now. With conditional caching on the big js file, it should only need to be loaded once per site release, so it should also be ok. On Sunday, January 27, 2013 9:37:32 PM UTC+1, Evan Mezeske wrote: I solved this problem for my web app in a different way, which might be worth considering. My entire ClojureScript project compiles to a single JS file which is used by every single page. I organized things such that each page had a cljs namespace associated with it, which has an init function. So for instance, /foo/bar.html would know to call (myapp.foo.bar/init) on load, and /baz/hello/world.html would call (myapp.baz.hello.world/init) on load. This is just one way to organize things, but it works pretty well for me. The advantage of this approach is that you only have to download the giant ball of JS once, and then it's cached for as long as you like. The disadvantage of this approach is that the giant ball is, well, pretty giant. I think that it makes sense to use the single JS file for reasonably complex apps, where your application code is small in comparison to the ClojureScript standard library. In that case, the whole JS file will not be much bigger than just the standard library itself. Of course, if your app is very large (several tens of thousands of lines of code), and you really need to get the initial JS size down, you will have to do something more sophisticated. On Sunday, January 27, 2013 4:54:59 AM UTC-8, Marcus Holst wrote: Building a traditional multipage webapp and using only some cljs code on the pages requires me to put all the cljs overhead output in one single file that can be cached by the browser (in order to not have to load the same 130+ k cljs overhead for each page). I've tried creating an empty namespace containing only the overhead compilation, and then requiring it from one of my page specific cljs files. However this just spits out endless amounts of warnings. Have anyone done this before? -- -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clo...@googlegroups.com javascript: Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+u...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/clojure?hl=en -- -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Minimizing the download of js code in Multipage ClojureScript webapp
Building a traditional multipage webapp and using only some cljs code on the pages requires me to put all the cljs overhead output in one single file that can be cached by the browser (in order to not have to load the same 130+ k cljs overhead for each page). I've tried creating an empty namespace containing only the overhead compilation, and then requiring it from one of my page specific cljs files. However this just spits out endless amounts of warnings. Have anyone done this before? -- -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: Minimizing the download of js code in Multipage ClojureScript webapp
Thanks Evan! I actually already started along this big js blob path and was just beginning to see the problem with clashing page inits. Your solution with an init func per page will probably do just fine for me too so I'll try that now. With conditional caching on the big js file, it should only need to be loaded once per site release, so it should also be ok. On Sunday, January 27, 2013 9:37:32 PM UTC+1, Evan Mezeske wrote: I solved this problem for my web app in a different way, which might be worth considering. My entire ClojureScript project compiles to a single JS file which is used by every single page. I organized things such that each page had a cljs namespace associated with it, which has an init function. So for instance, /foo/bar.html would know to call (myapp.foo.bar/init) on load, and /baz/hello/world.html would call (myapp.baz.hello.world/init) on load. This is just one way to organize things, but it works pretty well for me. The advantage of this approach is that you only have to download the giant ball of JS once, and then it's cached for as long as you like. The disadvantage of this approach is that the giant ball is, well, pretty giant. I think that it makes sense to use the single JS file for reasonably complex apps, where your application code is small in comparison to the ClojureScript standard library. In that case, the whole JS file will not be much bigger than just the standard library itself. Of course, if your app is very large (several tens of thousands of lines of code), and you really need to get the initial JS size down, you will have to do something more sophisticated. On Sunday, January 27, 2013 4:54:59 AM UTC-8, Marcus Holst wrote: Building a traditional multipage webapp and using only some cljs code on the pages requires me to put all the cljs overhead output in one single file that can be cached by the browser (in order to not have to load the same 130+ k cljs overhead for each page). I've tried creating an empty namespace containing only the overhead compilation, and then requiring it from one of my page specific cljs files. However this just spits out endless amounts of warnings. Have anyone done this before? -- -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
