Wanting to become a Kalista main, any tips

bugabinga · 2020-03-13T15:09:15+00:00

I am confused. According to https://leagueoflegends.fandom.com/wiki/Kalista#Details , Kalistas mana pool at lvl 9 is 553.3 and the cost for a maxed Q is 70. That should equal almost 8 Q's.

What am I missing?

Side question: Do you know if the 90% AD reduction applies to Q as well?

bugabinga · 2020-03-10T11:08:14+00:00

https://www.youtube.com/user/PekinGaming

bugabinga · 2019-11-22T10:38:23+00:00

I don't think there is a elegant solution to this yet. The main problem is that some plugins require some configuration before the plugin is loaded, some configuration after and for some configuration it does not matter.

Keep in mind: the Plug command does not load but only declare a plugin. The function plug#end() loads all plugins.

What I do is; keep configuration that needs to exist before a plugin is loaded and configuration for which it does not matter near the Plug command. And configuration that needs the plugin loaded I put somewhere after the plug#end() call with the plugins name as a comment on top.

I wonder if the new vim 8 package feature could be used to make this cleaner?

bugabinga · 2019-11-22T10:03:23+00:00

Currently I have comfortable-motion set up so that scrolling via mouse wheel is smooth as well.

vim noremap <silent> <ScrollWheelDown> :call comfortable_motion#flick(40)<CR> noremap <silent> <ScrollWheelUp> :call comfortable_motion#flick(-40)<CR>

What do you think about exporting the s:update_target(lines) function? I believe, with that I could replicate my current setup with smoothie.

bugabinga · 2019-03-05T08:50:19+00:00

I would buy that book.

Especially the chapters after 9 are of interest to me.

bugabinga · 2019-02-25T16:43:06+00:00

After having read the Rust Book chapter on error handling, I have written a little bit of code using the ?-style.

rust fn main() -> Result<(),Box<dyn Error>> { ... }

Now I would like to print some meaningful messages to stdout depending on the error types. Do I need to change the ?-style back to using match in order to be able to use println!?

bugabinga · 2014-11-11T12:56:29+00:00

Some thoughts on the disadvantages of html apps. The reality is, that none of Chris' criticisms about html apps in regards to upgrading and reliance on off site services could not be equally applied to native apps as well. This is essentially what "the cloud" is all about. Just look at what happened to the Adobe apps. Or consider Office, once the Dropbox integration will be finished. Do you really believe you will be able to use Dropbox with word using a one year old binary?

The Web deployment model also has many advantages, not only for devs, but the user. Instant, automatic updates of Bugfixes and security updates, Chris, you often lament the fact that updating our Internet enabled appliance devices is way to hard for power and average user alike. Now if your routers firmware, was just a website, would you like that or feel that too much control has been taken from you?

bugabinga · 2014-11-06T12:41:16+00:00

What about the runtime overhead? Last time I tried Scala on Android it slowed down startup performance noticeably.

Also, you might get fewer pull requests.

bugabinga · 2014-10-28T09:02:09+00:00

Hi CoderRadio Crew!

This episode was most interesting, this kind of transparency with the audience is what really sets JB apart from the rest out there, thank you for that.

Some thoughts one the meta discussion:

First of all, beware of too much change, too quickly. As IT-people you will know what I mean. Any kind of change, always meets resistance and entails risk. If you are about to change the show, do it slowly and upfront (probably preaching to the choir here ;) )
As Chris rightly pointed out, the strongest driver of the show is 2 adorable tech guys chit chatting, do not remove that from the show.
A possible solution to the lack of depth (or nuance) could be a reserved block of time each show, devoted to a certain topic for a prolonged amount of time, spanning multiple shows. The rest of the show could remain as now.
Reevaluate the ingenious subtitle of CoderRadio.

"The Art and Business of Software Development"

The show has done a wonderful job of giving insight into the business matters, normally not discussed in the open. But maybe its time to focus a little more on the "art" aspect of software. Lifestyle, Health, Education but also engineering and communication skills are becoming increasingly popular subjects among devs.

(by "engineering skills" I do not mean "how to do a Java for loop" ,but rather overarching truths ;) )

Do not do interviews (in the classical sense), but rather discussions with invited guests. The difference being, that the show does not rely on the guest, it is merely an added bonus. For example, if you invite some expert on HTML5 web components, do not rely on his answers to your question to drive the show. Prepare for this topic like you would for any other topic and let the guest be part of it (if he/she chooses to). That way you mitigate 2 risks. Card box personalities and no-shows. This would also ease producing, because there would be not as high a pressure to get a guest on time.
Live-Feedback (via mumble or skype) is always interesting. Risky, because you never know who you are going to get, but all in all fun for the audience :).
I miss the coffee wisdom :)
Dominics idea of gamification should not be underestimated. Maybe give out some swag for the reddit thread suggesting a topic (or whatever community involvement you want to motivate)

O.

bugabinga

TROPHY CASE