Roadmap please

[Jamz]

You may also want to try some XP/Paired programming if you have newer devs. It may seem like a waist of resources to have 2 developers working on the same issues but the amount of context sharing and knowledge transfer you get is better than having a new dev "figure things out" on his own for a whole sprint.

[kbs666]

Originally Posted by Jamz

You may also want to try some XP/Paired programming if you have newer devs. It may seem like a waist of resources to have 2 developers working on the same issues but the amount of context sharing and knowledge transfer you get is better than having a new dev "figure things out" on his own for a whole sprint.

As a project manager I've tried pair programming to bring new/junior devs up to speed and it has always been a dismal failure.

Finding two coders who think/work the same way is just not realistic. The senior also likely knows the system and knows exactly how to fix the problem/add the feature and finds it frustrating to explain everything. The senior dev doesn't get work he should be doing done and the junior doesn't really do anything and likely doesn't learn very much since he didn't do all the tracing of code and exploring that would have been required for him to do the task himself.

[evildmguy]

Originally Posted by kbs666

As a project manager I've tried pair programming to bring new/junior devs up to speed and it has always been a dismal failure.

Finding two coders who think/work the same way is just not realistic. The senior also likely knows the system and knows exactly how to fix the problem/add the feature and finds it frustrating to explain everything. The senior dev doesn't get work he should be doing done and the junior doesn't really do anything and likely doesn't learn very much since he didn't do all the tracing of code and exploring that would have been required for him to do the task himself.

Well, when I did it, it worked well, on both sides. Yes, paired programming probably works best when they are at similar programming levels, and one is merely teaching the other the code and how things are done there. It can be done.

We followed the rule that one person had the keyboard for an hour while another looked things up or helped. Then we switched. Worked very well. When I was the junior, I might have had the keyboard for two hours to their one, but it did help a lot.

I'm not arguing that you have lost productivity. That will always happen when you onboard someone because it takes time to get them up to speed. When the company I was at did this, though, within a (two week) sprint, I could take stories on my own. I wasn't fast and code reviews were important but I could do something. That helped for my own sense of accomplishment.

I have also found that a lot of places don't implement Agile/Scrum well, usually on the business side. The business treats it like a buzz word to attract people, not realizing they have a big part to play in it.

But that's me and my own experience.

ETA: I would also say that both as the person teaching and being taught, both sides learned a lot. Having to relook at past code or think about things "they know" made them understand it better themselves. It also made them better teachers when they could see it from that new angle and explain pit falls.

[Greebo]

Originally Posted by BJ

Of course there are! However, since I don't know at this juncture which ones will be practical and which ones won't, I wouldn't want to get anyone excited only to have to remove them. Once we have the time and resources to thoroughly investigate the incredibly long list of ideas and requests we have I can put together something more informative.

Sorry to push, but do you have at least an idea, how long it will take to investigate the list and tell us, when to expect further updates?

[daplunk]

She's saying, politically, that they are not going to provide a list. And that they are not currently working on Realm Works.

[Greebo]

Originally Posted by daplunk

She's saying, politically, that they are not going to provide a list. And that they are not currently working on Realm Works.

Yes, I know. And I was trying to ask politely, when they are going to resume working on Realm Works.

Or wether I should start looking for alternatives.

[Exmortis]

Feel like I am watching Battlestar Galactica.

"All this has happened before, and all this will happen again."

Groundhog Day here again.

[goddelusion]

Originally Posted by Happydevil43

Sadly I am one of those.

As I generally only play published adventures (ok, I started building my own homebrew campaign, but just gave up - I dont have the time to devote to it, between playing and DMing in 4 games a fortnight) , the shiny buttons of new actively developed toolsets such World Anvil and Arkenforge are calling me.

I will still have RW for any campaign type stuff... but for individual sessons and as those systems get more and more features like RW (really its only autolinking that holds me back).. I'll find that I'll use RW less and less.

I havent given up hope yet... but what I want from a toolset is changing.

I must admit that I too have grown tired waiting for RW to be something more than a 'passion project' for Rob and the Devs. It is frustrating to have a tool that shows so much potential, but lacks internal support. You have a Ferrari but are running it on a Volkswagen budget. I will continue to keep RW installed but at this point, It will be my 'passion project' and treated with the same level of interest as is shown by Lone Wolf...minimal. I'm going to put my effort (and $$$) into World Anvil at this point. Here's hoping that RW's 'some day' becomes 'today'.

[Conandy]

Sadly, when I started this thread, my intent was honestly to give LWD the opportunity to show that they still have some love for RW and for this dedicated group of game masters who love the tool and are begging for it to evolve and to be loved by its creators. But instead of taking a day or two of time to put together any kind of road map that could be used to start these discussions in the right direction, to re-affirm support for us and from us, they have essentially put a nail in the lid of the coffin of RW.

It truly saddens me that I have invested so much time and effort in this tool on the false promise that it would continue to evolve and become something more. But alas, I think that, beyond continued use for the campaign info that I already have in the tool, I am probably soon to be done with RW. My $ and time and loyal customer-ship will likely go towards World Anvil or Yarps as I develop a new homebrew D&D campaign world.

[Lj Stephens]

Hi folks. We really do appreciate that you have so much interest in RW. We do too. We are working on it, and on HLC, and on HLO as fast, and as efficiently as we can. We completely understand your frustration. Please understand that this is an ongoing process with several brilliant minds working things out. I'm sorry we can't give you a more solid answer at this time. Please continue to be patient and we'll let you know what the roadmap looks like just as soon as we are able to. Thank you.