entrepreneurship, Flipping, Goals, Hard Money, hustle, Hustle Estate, Improvement, Leadership, Learning Lessons, Purchase, Real Estate, Rehab, success, Technology

Hustle Estate – Flipping Homes 101 – Ep 5

Flipping Homes 101 – Ed and Isaac walk through the overall process it takes to flip a home. Ed talks about where he buys homes from, what to think about when looking to flip a home and how to get a hard money loan.

Feel free to reach out with questions or comments on Twitter/Instagram (@HustleEstate) or send us an email HustleEstate1@gmail.com

Happy hustling!

 

Music – Showtime by Artlss – https://www.melodyloops.com/tracks/showtime/

Advertisements
entrepreneurship, Experience, hustle, Hustle Estate, Leadership, Learning Lessons, Real Estate, Technology, Tools, Uncategorized, Vision

Hustle Estate – Buying Your First Home – Ep 4

Questions or comments – reach out to us!
Twitter/Instagram – @HustleEstate
HustleEstate1@gmail.com

Looking to buy your first home? We have some practical tips to help you find the home of your dreams. Both of us share our experiences buying our first homes (multifamily and condo). When we started looking, we had some ideas of what we wanted, but after we made our purchases we learned a lot more. Learn from us so you don’t repeat some of our mistakes.

Happy hustling!

Hustle Estate, Leadership, Learning Lessons, Real Estate, Technology, Tools

Hustle Estate – Career Pivoting to Real Estate – Ep3

 

iTunes & Google Play

Learn how Ed made his way into real estate. Ed’s career didn’t begin in real estate. He was curious about owning property at a young age, but started working in non real estate financial institutions after college. Once he bought his first property, he quickly realized he’d rather spend time understanding the real estate industry than other financial businesses.

Feel free to leave us a comment or send us an email at HustleEstate1@gmail.com

Agile, Estimation, Improvement, Leadership, Remote, SDLC, Technology, Tools

Daily Sprints – Day 9 (the last day!)

The LAST post! I posted for the last two weeks about the previous day to provide interesting insights on how the team is trying to improve their estimation! See Day 0, Day 1, Day 2, Day 3, Day 4, Day 5, Day 6, Day 7 and Day 8!

What have you tried that works or doesn’t work?!

Day 9 – The Last Day

The last two weeks have been amazing. I will spend some time later this week reflecting and writing about the overall process. Last Friday was really our last full development day and we were finally in our Beta environment.

All we needed to do on Beta day was some small testing. So we needed to figure out what we wanted to accomplish.

Our goal for the day:

  • Take some time to learn a new version control that we are moving towards soon
  • Add some more integration tests
  • Get a quick POC for an API call to an outside vendor we haven’t used before but plan on using soon

What did we accomplish:

  • Added integration tests
  • Created a plan for our engineers to get ramped up on the new version control
    • Our Sr. Engineer has some experience in this so they are going to spend some time getting back up to speed
    • The other two engineers have limited experience and will work with our Sr. to help gain knowledge in the tool
  • API call POC – Done!
    • After we set our goals, the team came together and pair-programmed a solution to get a call to this API
    • This was accomplished within two hours of setting this goal, which was amazing to see!

Retro:

What did we do well?

  • Quick POC and pair programming
    • Got exposure to the XML
    • Also started to brainstorm questions for more work on the API integration
  • Beta testing went well

What can we do better

  • Look back at and bring back our production push checklist so we can think less about what we need to do when we push our solution to production.

Overall, it’s been a great nine days of trying something new on the team. I hope anything you’ve read helps you think about ways to improve your team!

(Featured Image Credit: http://changingthegameproject.com/winning-race-right-finish-line/)

 

Agile, Estimation, Improvement, Leadership, Remote, SDLC, Technology, Uncategorized

Daily Sprints – Day 8

One more post for Day 9! I will post about the previous day and hope to provide some interesting insights on how the team is trying to improve their estimation! See Day 0, Day 1, Day 2, Day 3, Day 4, Day 5, Day 6, and Day 7!

What have you tried that works or doesn’t work?!

Day 8

Better late than never – I prioritized other work that directly impacts this team over getting this post out this AM. 😦

Goals for the day

  • Show N Tell of all the features we are pushing to prod to the business this build
  • Begin to think about technical design behind our next big project
  • Finish UI Integration issue
  • Identify if we can add a small UI enhancement to one of our solutions

So what did we accomplish?

  • Everything we set out to do the for the entire 2 week build, including in Day 8!

Day 8 was special! This was our code freeze day and a few amazing things happen – to be honest, a lot of amazing things happened over the last seven days.

What was so amazing?

  • UI Integration
    • This was a broken file due to an encryption and environment issue. The process we went to solve this problem was amazing to watch!
    • Our Sr. Engineer sent an email the night of Day 7 to one of our other Sr. Engineers to help us think through the issue. The next morning we had no response. During our goal setting meeting, I challenged the Sr. engineer to call someone to get an answer. This didn’t happen…
      • A BETTER IDEA HAPPENED! Our BA suggested we bring in people to our Zoom call and then our entire team can hear about the problem and ways we are trying to solve it so we can learn together. This was a great idea!
      • The other Sr. Engineer on the infrastructure team called into our Zoom and helped us brainstorm, but no luck.
      • We brought another Sr. Engineer in who had knowledge of this solution – no luck.
      • Finally, we brought an Architect in and they helped us identify the issue solely because they understand the differences in environments! Once the Architect helped us make that connection we solved the issue. Amazing!
  • Business Show N Tell
    • This Show N Tell was different. I think because the team was so happy at all their accomplishments over the last two weeks (as they should be).
    • What was really interesting was the reaction to the business users when we said we solved some tough technical challenges while trying a much different way of operating.
    • I didn’t anticipate this. After our BA brought up the different way the team was doing things this build, I mentioned I was blogging about the journey and sent the blog link to the leaders that were in the meeting
      • This is interesting because I often think the business users and leaders see technology as a black box. Here is a problem (input) and technology provides a solution (output). How tech teams go about doing their work is not something our business users and leaders see very often or at all. My blog posts provided a nice insight into our process, without even thinking this could be a tool for them. I hope anything they’ve read has helped them understand how we operate a little bit better.

Retro

What went well

  • UI Integration Solution and bring people into our Zoom call
    • Helped us focus on solving the issue
    • Resolved it quickly
  • Show N Tell
    • Went well and business leaders were happy without solution
  • Overall the last two weeks have gone really well
  • Team picked up some small stories at the end of the build with UI tweaks – great we could bring in some more work!

What can we improve?

  • Time box ourselves more often to reach out to help sooner
  • Bring in people to Zoom more often rather than calling – this may be a big game change for us as a remote team with 99% of team members in Detroit.

Have a great weekend!

(Featured Image Credit: http://uncomonresilience.com/winning-in-life/)
Agile, Estimation, Improvement, Learning Lessons, Remote, SDLC, Technology, Tools

Daily Sprints – Day 7

Each morning for the next three days, I will post about the previous day and hope to provide some interesting insights on how the team is trying to improve their estimation! See Day 0, Day 1, Day 2, Day 3, Day 4, Day 5 and Day 6!

What have you tried that works or doesn’t work?!

Day 7

Every day this build, the team continues to show progress in thinking about how can we do better, even when it’s unrelated to the process of getting work done! Day 7 highlighted great examples of challenging each other for a better ways to solve problems and a bunch of collaboration between the team to push past issues.

Our goals for the day

  • UI Changes
    • The past two days, one of our engineers tried multiple solutions to solve this issue with little luck. They were understandably getting frustrated
    • Before moving on to discuss other goals, we talked about the process the engineer was taking to test their results, and we found that the engineer was taking a long time to see results, so we dove into their local testing process
      • Other engineers challenged the process this engineer was going through! It was awesome to see and the other engineer took the ideas in stride (see results & “what did we accomplish” below)
      • Examples of challenges
        • Why do you need to run all the services when the solution you are working is only using one service?
        • Why do you need to stop the services when you make changes?
      • Result: The three software engineers would spend one hour after this meeting going over the issue and thinking about what could be done – rather than the one engineer continue to try other ideas on their own
  • Message story bug
    • After we had the message solution in our test environment, we discovered a bug that needed to be fixed
  • Config switches
    • We were waiting on our DBAs to run some scripts and then needed to test those results
  • UI Integration fix
    • Issue was investigated in Day 6, now we wanted to solve the problem

What did we accomplish?

  • Config switches – done
  • Message bug –  fixed but more testing to be added
  • UI integration
    • Still working on the issue. We identified that we were missing our credentials file and now we just need to identify the file location
  • UI Changes – FIXED!
    • This was a great example of team work
    • After our goal setting meeting and the challenges towards the engineer who was taking on the work, the three software engineers came together and started to work through the local testing process that one of our engineers had been using for the past couple of days. The engineers identified two things to try that ultimately led to this story being fixed
      • One engineer helped demonstrated the waste behind running all the services, when we only needed to run the one that mattered to the solution
      • Our Sr. engineer helped point out how we could use Internet Explorer to better test CSS changes
    • After trying these ideas out, our engineer was able to solve the issue!

Retro

  • Code reviews
    • One of our engineers added a task for code reviews. This sparked some ideas if we should add these tasks to all of our stories
    • Another idea was to add a “tag” to a task to identify if the story was waiting to be code reviewed
    • Another idea that came up was adding another column to our Kanban board for code reviews
    • We are going to see if we can add a column to the Kanban board and if we can’t, add tags.
  • Talking about what went well
    • This was a great point mentioned by our BA. We’ve been using retro to just focus on how can we do better, but haven’t been celebrating our wins for the day.
    • Moving forward we will celebrate what went well, as well as, identifying what we can improve
  • Quick Business User Feedback
    • Great example of a fast feedback loop & communication progression
    • Our engineer noticed multiple data points that were coming in from different dates. The Engineer and BA talked about if we could just show the one data point or needed to show all of them based on date
      • This started as an instant message conversation and moved to a phone call. They recognized that they could get an answer from our end user
      • They called the business user to help make the decision
      • Once the business user called in, they got a quick answer and were able to finish the solution based on the feedback from our business user

Only a few more days left in our two week build!

(Feature Image Credit: http://www.corporatecomplianceinsights.com/the-light-at-the-end-of-the-tunnel-or-cliff/)
Agile, Estimation, Improvement, Learning Lessons, Remote, SDLC, Technology, Tools

Daily Sprints – Day 6

Each morning for the next three days, I will post about the previous day and hope to provide some interesting insights on how the team is trying to improve their estimation! See Day 0, Day 1, Day 2, Day 3, Day 4 and Day 5 here!

What have you tried that works or doesn’t work?!

Day 6

Day 6 started well with no major issues! Our Sr. Engineer got his computer ready for development. Everyone had ample time in their calendar to work on development tasks! Pretty great that everything was working. What I personally found interesting over the last couple of days was how often things unrelated to our solutions come up that can take down development time.

Our goals after starting the day

  • Finish writing integration tests for the messaging story
    • Found a merge conflict because a file was moved outside the unit test solution
  • UI story
    • Testing last night, hard drive space prevented her from running the services
      • Cleared about 10 gigs
      • Code review out today
  • Configuration switch for one of our services
    • This was challenged by one of the engineers on the value of this over some other work in our backlog – we did end up working on it when we looked at our remaining work.
      • Great challenge here!
  • Investigating an issue with a UI integration that is broken

What did we accomplish?

  • Integration test were checked in, but there were questions about the software solution being pushed to our test environment
    • This is happens sometimes because of the schedule of when we push work to our non-prod environments. Our teams don’t have the ability to push work whenever they want due to a number of things. It does cause issues at times and prevents us from getting a faster feedback look (this is being worked on by another team)
  • We solved the merge conflict
  • We met with an Architect to get a Git project set up and build out an analysis tool for one of new projects that we started earlier this week (the messaging story)
  • UI Story
    • This story is making progress, but we weren’t able to check in any work. This solution utilizes XSLT which is not something we are very familiar with, so there are a lot of unknowns
  • Config Switch
    • We did end up working on it but we are road blocked with a DBA tasks to see if it is working
    • This also goes back to earlier in the week about calling out roadblocks earlier so we can be better at planning other work while waiting on roadblocks
  • UI Integration investigation
    • We were able to reproduce the issue but we can’t identify the cause due to the layers of UI elements that isn’t allowing for the error to be logged correctly
    • Our engineers plan on trying to add logging or find the error logs in the coming days

Retro

  • Working in different time zones
    • This is a unique problem to an all remote team. The team has team members on East Coast, Central and West Coast time zones
    • Our BA and Engineer in central time, set a meeting for 2:30. The BA thought 2:30 EST and the engineer thought 2:30 CST
    • We decided on defaulting all times to Eastern time and leave the responsibility of “translating” that time for the team members in their respective time zones
  • Offline files continue to cause issues
    • One of our engineers couldn’t run their solution because their hard drive was full
    • The engineer identified that about 50 gigs worth of files sync every evening, and they need to delete those in order to save space
    • This is another unique challenge that our engineers face at times. The awareness around this issue was great because they helped explain what to look for and the manual work-around of deleting the files until
(Featured Image Credit: https://www.naylor.com/associationadviser/advertising-during-economic-recession/)