 Yeah, yeah, yeah, yeah one two two two two. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. All right, so has the super user password to set up fully on the application that I hear, but what tools would you, any tool that you would suggest that we use for that? I have not actually used that for Chupol per se, but that's a good practice. I would recommend that. And like for everything else in Chupol, there's much for that. I'm pretty sure. VPN is something that I hate as a remote user. And if you have lots of different VPNs that you have to strap around logging this VPN and then you push something and you pull something from another VPN, the overhead that comes from that is just going to be annoying. And that's actually stopping me from working for a few projects. Like for that afternoon, I have to do a small push or something. I'm not going to get the VPN. But there are tools like browser based VPN, which makes it easier for you and preset tools and all that. But it's a good practice to have if you have an internet that you need to help people to access. But in smaller teams, VPN is usually not that important. That's for security. The fourth thing is keeping their schedule. And that's what I discussed quickly before with people going overboard and working all of the day, all of the day. So fixed work times, not too fixed, but keeping them around business hours back and forth a bit and giving it relatively flexible, but not too flexible is a good practice. So pretty much what we do is work from nine to five. And if we actually have to do something, then of course, we get that time free anyway in a lot of ways. But if you allow completely flexible time with people and the people are really motivated, they will work too much and they will burn out easily and annoy other people with team sending messages in the night. And I've actually had a call from a client, like another client, but team member at two o'clock, like, yeah, we did that work. And I'm like, come on, call me tomorrow. But yeah, like you have to have some ground rules on the schedule. And it helps on pretty much every level. It helps with the clients as well when you're working on business hours. So all of the clients can contact you if they need to. This is a good idea. This is common knowledge in the remote work community to have an idea of a good day's work. Instead of going, I have to work seven hours. I have to work that every day I have to do a good day's work. And this is something that if you have flexible time, this is something that's really important. So what you have, the feeling that you have done a good day's work, you don't need to start or have a task. And this is something that's completely based on the trust that you have with your team. And if you don't have trust, this is something that you cannot do. But for example, if you work from nine to five, and at four you have finished the task, and you know that it will take you a lot of mind power to get the next one going, you can just say, okay, I did a good day's work, I'm done for today. And everyone in the team will appreciate that. Rather than doing all every day eight hours, you can do more productive hours instead of just working on the computer and say, doing that homework out. Workflow is something that's really important for every team, even office-based teams. And workflows usually get out of hand really quickly. A good workflow is something that you can easily prioritize the tasks, but you're not wasting everyone's time. So back in Finland, we had a 25-person team, and we were working on a project that had a product owner, and all those 25 people were in every meeting. We were working on Scrum, and Scrum is good. But usually, this is the idea of Scrum, but usually what happens after you implement Scrum is something like this. So we were pretty much losing an hour, a day of a week, everyone in a team for just going to different meetings. So we were having sprint planning, sprint review, daily meetings, and then we had backlog crewing, students, so that was a day out of every week. And that was times 25. So you have to keep it simple so it doesn't go like this. So either get a good project manager or split your team into different teams that have their own workflow. So this is the feedback from every developer really much on that team. And after some time, we decided to split the team into multiple different smaller teams, which use Ganman, which is a simple workflow, but of course, if you have a more complex client, it's really hard to make it work. And that's a really simple Ganman, or your board will have quite a problem, so whatever. Just my point is not to overcomplicate your workflow. Keep it simple, keep it so that you won't lose hours and hours on meetings. That's the name of the board concept. It keeps it really simple. It's a ticketing-face system. They are good tools like Trello, and just keep it simple, not going to complain. Is there people working with Scrum? How do you find Scrum? Scrum is great, but it has issues. How do you find it? I'm finding it really good as well. There are so many different tools out there, you just need to find the one that works for you and finding the right workflow at the same time. So if you don't know what you're doing and it feels bad, then it's okay to try Scrum. As long as you don't do it all the time. So that's the main point that I want to make about great flows. To keep the overhead down, because most of the developers want to work instead of taking in meetings. And usually if you go to a meeting, it's going to be so that the developers are working on their computer all the time when they are in the meeting. So keep your overhead down. And then there's lots of other things that I could go to, but I don't have enough time. So using the best tools, making sure that everyone gets paid well, and sending remote teams to clients can be sometimes hard. Reducing your distractions, that one's already there. And outsourcing is a tool that is used to, but you don't have to. Just make sure that you're not always using it. So to sum it up, I think remote work is awesome. And you should do it, but just do it right. Don't do what so many others do. And just if you're a big company, don't let some people work remotely. Don't create two cultures and do it right. So what I want all of you to get out of this is to embrace working remotely. Get other people to work remotely. Because it's a great tool. It makes working better. You get more productive. And together we can raise this number to this number. And that's what this whole shaking is about. And I want to encourage some discussion after this. And if you want more information, I have a book coming out about this subject in a month. So everyone can go there and get a free copy of it if they want. Yeah, thank you. And then some discussion. So any questions, Jack? Time sheets. Time sheets. Do you find there's issues with remote workers? What do you mean time sheets? Tracking time? Tracking time. Yeah. What we use is an open source tool called Kimeo. We track time for client work. But when we do our internal things, then it's all based on trust. We just say how much we work. But when we track our work with clients, we use that time tracker tool. It's almost a code. Kimeo. K-I-M-O. What was that? Minutes ago. Minutes ago. I actually found out that the big remote it's been a long time ago. Sounds like an Oscar. No, that's not an Oscar. Anything else? What about tools like Yammer in the box? Did you use that during the process for sharing files, managing versions of documents? Yes. Sharing files and having file access is really important. For development purposes, we use our own custom version of the file. And that's great for our purposes. But for files, if you have documents and all that stuff, we've been using Google Doc, which is Google service. So it's pretty much available anywhere. And it tracks your renditions as well. So that's what we've been using. And if you have any benefit, we should like not to hear it. We usually use box. Box, box. Yes. We have a company. We bought the package, but it gives them out. Then we deliver it to you. I think Google Doc gives them out. But we found that works really well. Especially to control the difference of access levels. Giving it out to the client for a certain period of time. Google even if they had to access some of the documents, they had to upload stuff. And we can control it with the comments and so forth. So we found that pretty well. We use Yammer more for the fun stuff. Fun stuff or even links that we find around. So we use Yammer and tag it with the hashtag. So whatever is being sent to you here, I'm going to put up those notes on my phone on Yammer. And everyone else in the company can access it. So that's what we do. But I'm sure everyone has to do that. Yeah, everyone has their own tool. I was just wondering, because you mentioned about video calls and chat. But in terms of just working on websites, there's a lot of files in terms of versions. Yes. Are you working with websites or? Yes. Are you working with it? Yes. Some of the developers, I'm not a developer. Oh, okay. The guys use it. But just in terms of the files and files and simple stuff. Because we did not plan to. Yeah. Get up for their files to come out securely. And then to give us their passwords and so forth. Yeah. We have actually used also a thing called VTC. Which is something that is hard to set up with clients because of the name. But it's actually a really good tool. It's pretty much like Dropbox, but you do it yourself. But that's a great tool for syncing all the data all around. Do you have a question? I was wondering how do you, what do you recommend for communication without making it sort of a disciplinary situation? Yeah, yeah. I understand what you mean. We actually have like, do you work with vits or other? Yeah. So what we usually do is we encourage communication. But if there are people who are not so happy to communicate all that, we have integrations with our vits. So that every time someone pushes something, we all get that into the instant messaging client. So we can see that they're actually doing the work. And that's still a communication. But it makes it a bit better to monitor, not monitor per se, but like keep track of what's going on. And it's also good for cold reviews. So if I push something, then Brian is there looking at my code and saying that you'd be bad here. But other than that, I know that it's hard to get people to do that sometimes. And if they're not capable to do that, I think they're not capable to work remotely. So, and then it goes to the conversation and that's a fun way. Yeah. I have a question. How do you, as part of your journey, stand-ups into your remote virtual? And how is that really, really time-out? Because are you... A lot of... I'm not. I don't think... What are your stand-ups? Yeah. Well, the... What about the type of text you see that you might be really like, you put up with the type of text and what I do, it's like you can stand up, not do anything else. Okay, so you mean like a day in the evening? Yeah. Yeah. And I can see that I can't do the running because we might not be able to do the stand-up. Well, we can, like... They were planned to be 15 minutes or 10 minutes, like, they're amazing, but they can't go up to maybe 45 minutes. And that's good for the social part of it, but in any case, their time-out would be much better. Anyone wants to do that? I've heard also that... You know, I don't actually go to... Everyone's going to need to be related as well. The social aspect is great, but if someone's like, I'm locked in these, you go, well, what's the time? What's your project to call? Yeah. Anything else? That's also one thing. The team size is one of the stand-ups. Why don't you stand up and try to distract the three people in one minute at a time and join the next? Sure. Have you had experience with the social business software, like Jive? No, not yet. That sounds pretty interesting, but do you have...? I haven't, but we've got multiple locations, and we're trying to think of ways to see the best ways to build a corporate culture across different, you know... Yeah. And, you know, obviously, divergence, you know, like things, you know, I'm obviously from my own culture, and I'm obviously from Australia. We don't have time to sit around and talk on the internet, right? Yeah. Which is... Yeah, of course. So, you know, I'm just not sure how useful some of these tools are, but I mean, integrating them with... as you just mentioned, like it's a real part of the workflow that we can... Yeah. Yeah. Yeah, it might be for you to try, but just don't, like, spend too much time on it. Yeah. I mean, if you watch that, it's good for everyone, but it's a good tool for... a tool for... No, no, no, no. A tool for companies, like at Jive. Yeah. Yeah. I'm aware of it. It's pretty much. That's what... Yeah. But I think the keys have one tool. You know, they're a centralized point, so we'll use red line for that problem. We're pretty much done on time here, so thank you, and thank you, and... Thank you. Thank you. Thank you. Yeah. Oh, yeah. Yes. We actually use Google Hangouts for, like, pair programming, so we share each other's screens and we can see what we are doing, and then if... As long as it doesn't go to, like... We've been doing that as well. Yeah. I think it works. It's kind of hard. It's something else. I'm trying to sell a bit more. Yeah. Yeah, we did something like with Google Drive, that we actually put the code there, but there's no code syntax or anything, so it's kind of hard, but we... Like, you can both do it on the same time, and if there's... If you find a better tool for that, I would be really happy to hear it, so pretty much a PHP storm or something like that, but we're together. Yeah. Yeah. We had fun. Yeah. Yeah. Not too much. Hi. Yeah. I was missing your, uh, presentation. Was it? No, I got it there, so I'm going to put it down. No, I got it there, so I'm going to put it down. Oh, that's like... Our entire team is... Yeah. We built a team, but the company's built us up. You had a streaming platform. Hmm. That's not good. That's not good. Yeah. Yeah, I'm going to put it online. Yeah, I'm going to put it on. I'm going to tweet about it on the triple south side. And, which company are you from? Reality is one. Okay. So, we're going to start? Yeah, where are you based on? We're just three people now, but I was... Before, I was going to find much bigger confidence in... And we had to stop. Yeah, we had to do that. We had to stop. Yeah. You know, there are a couple of you guys, so we can see if we can get in. Oh, yeah. That's good like there are a couple of them. Yeah. That's pretty cool. If you want the contact, know where we are, get information of the company at the stores. Yeah. Can you tell us what you guys are doing at seeds? Do you remember the name? The three-part. The green channel is one of the... Yeah. No, the... The five-part. Finish guy. Yay! I think he actually quite, But I can get you to touch with someone if you want.