Loading...
Answers
MenuMy team leader is stuck in his ways. Our product doesn't use a framework, he doesn't use design patterns or new tech. How can I instigate change?
This question has no further details.
Answers
First, realize that change isn't an overnight process - it can take time to make the case for trying something new to your superiors. Second, try to understand (if possible) what motivations your team lead could have for being "stuck in their ways" - this can provide clues on the types of strategies you can use to help persuade them of your perspective.
Instigating a change often requires understanding the context or situation you're in, which is likely beyond the scope of this question. However, a good place to start is by reading Mary Lynn Manns and Linda Rising's book, Fearless Change: Patterns for Introducing New Ideas[1]. It provides a series of change event patterns that you can adopt/adapt for your purposes depending on the situation you find yourself within.
A key takeaway from the book is to keep your skeptics engaged - don't distance them from what you're doing, but also don't let them dissuade you from trying to bring about positive changes. Another is that when you start this process, be prepared for the long haul. It's a lot of two steps forward, three back.
Good luck!
[1] http://www.amazon.ca/Fearless-Change-Patterns-Introducing-Ideas/dp/0201741571
There are different approaches that work for different people based on your comfort and personality. I am highly uncomfortable confronting people. So I try to influence people to see the point over a period of time. BTW, you should probably read the book "Influence without Authority".
Most people respond well when you make problems to be about the company, and about learning/trying out new things, rather than about a person and their ways.
"Hey! I am keen to see how using a framework can help our product. I am looking at some great examples and their cited benefits, and was wondering if we could manage to shift towards using a framework over the next quarter. I know there is a lot on our plate, but I'd be glad to champion this effort. Won't let you down. What do you think?"
I've seen some people use "insult into action" methods as well - where you question someone casually(should not be seen as harmful) in a public situation. Like in front of the CTO, ask an innocent question "Hey TeamLead. Why can't we use XZY design pattern for this? Is there a reason we never use design patterns? I'm sure you have a reason and I'd love to understand."
Change for sake of change or new tech for its own sake isn't anything good.
But Seeing different aspects/qualities of same thing and not communicating it across is also no good.
Maybe you are above him/her. Make sure you both have noses in same direction, looking at same thing+aspect AND talking about it. Try to live in each other shoes. Commucate a lot. About the why's. Anyway, at the end, It's all your fault, and there is one tough managers choice - change People or Change people. Including you.
Or may be you're under him/her. Have a look at Organisational patterns book (James Coplien, Neil Harrison, http://www.amazon.com/exec/obidos/tg/detail/-/0131467409/). Find some really matching one and leave it "accidentally" by the printer. Yes, organisational, not technical. Technical may follow, later, as they are response/solution to something. Find/point out that something that needs being solved.
In any case check the "Resistance as a resource" (D.Emery, http://dhemery.com/articles/resistance_as_a_resource/)
and... be careful. Change can be .. demanding.
Do not go and tell him straight on his face that you feel he has taken a wrong turn. No leader wants to hear that. You can give him tips as to how using design patterns will help him out.
If you want to use this technique, you need classes that fulfil four basic roles. You already implement three of these four roles by following the dependency inversion principle. The service and the client are the two classes between which the dependency inversion principle intends to remove the dependency by introducing an interface. As you can see, dependency injection is a great fit for applications that follow the dependency inversion principle.
You can read more here: https://stackify.com/dependency-injection/
Besides if you do have any questions give me a call: https://clarity.fm/joy-brotonath
Related Questions
-
What's the best way to build a MVP web app that handles order management, purchasing, invoicing, supplier management and inventory?
The best way to build an MVP for any SaaS product is to create a landing page that looks like a real product. Here's an example of one I built. http://www.happiily.com In this case, it advertises the primary features of the product and invites people to sign-up. When they do, they are asked for information which qualifies the person and then sends me an email. I built this quickly and very inexpensively and started getting inbound leads from it shortly thereafter. I got on the phone with each person who signed-up and explained the features I wanted to build and was able to do a lot of customer learning based on that. Happy to talk to you in a call if you'd like to talk more about customer development with SaaS products.TW
-
How should the dynamic between a ux designer and a developer who are working together look like?
It depends a lot of in the skill sets and experience of both people but in most cases the ux designer should be controlling the developer pretty heavily in order to make sure his ideas come through properly. The UX designer may just need to work on his approach so people don't feel bossed around and more like they are working together. In an ideal world, there would be a project manager who makes sure everything is communicated well and keeps the dynamic feeling great.JM
-
Which is the best hosted free bug tracking tool for a team size of up to 10 members?
Being a freelance developer for the last 10 years or so, I have seen and used almost every project management software you can think of, open-source and closed, and I have found that the "best bug tracking tool" completely depends on your process. I employ and direct teams in an Agile process that involves loose story-based requirements with point-based estimates, two-week cycles of iterative development, planning and retrospective sessions, and look-ahead and show-and-tell meetings with the stakeholders. It's important to me, then, that my tools have a method of capturing all those pieces with as much detail as I need but no more. On projects, I've successfully used Pivotal Tracker, Unfuddle, Redmine, Codebase HQ, Basecamp, Trello, and many others. I usually recommend people to Trello for light, agile management; it's essentially a digitized version of sticky notes and swim lanes. If your team actually needs a full-featured ticketing system, see Redmine (Rails), Trac (Python), or Mantis (PHP), depending on your language preference. Hosting a version of these yourself is fairly trivial, and numerous options exist for cheap or free hosted versions. For something in the middle, Github Issues is a good fit and the open-source clone GitLab.org replicates most of those features nicely. However, if you're looking for a hosted version, you're probably looking to offload that tricky "backup" thingy, and in that case, how important is your data? How proprietary? What's your business model? If you're working on an open-source project, Github will give your team a free account with private repos, issues, wikis, and the like. If you're okay with your project being "readable by all", public projects on Pivotal are still free. I'm mostly a consultant these days, leading small groups of junior or intermediate developers into a more productive, more mature, fully operational teams of senior software developers. One of the first things I teach folks is how to use a project management system... and why! It'll save your bacon if it's simple, effective, and reliable. With a few minutes of discussion about your project, I can probably help you select the right tool and service for your team. Let me know if I can help with that. Best of luck!DR
-
How can a small offshore development company find companies/software sales people to sell their service in the US/UK?
My company does a lot of consulting with offshore firms who are looking for a way to generate new business, so I hear this question a lot. My first reaction is that you need to totally reverse your mindset when you talk about your own company. You mentioned that you have: a great software developers team, proven track record, passion, real value But, everyone says that. There a 10,000 companies that have those things, so a customer isn't going to notice it. You need to figure out what your company is best at (doesn't have to be technical) and present it as a solution to a specific problem that clients have. Maybe a speciality, or really good project management, really good communications, a special expertise or experience, a personality, experience with a certain type of client.. really anything.. But, there must be some thing that makes your company 'special' otherwise you will be lost in the mix. Don't worry about things like rates, or the fact that you have 'great' developers. Those are generic. Think about why a client would really choose you, and try to build on that! After you understand your company identity, it gets much easier to identify and engage marketing channels because you understand your target.DH
-
How do you get a product prototype developed in China sitting in the US?
It varies and it's very very specific to what you want to develop. The concrete design of your circuit matters. Also prototype building costs are usually a factor 10-100 higher than series. If you already have your prototype then you can shop around various manufacturing companies. To do that, you need Gerber files (your PCB design) and a bill of materials. You also need to think about casing: designing it and creating the mold is expensive. If you don't have your prototype yet, I recommend having it engineered in eastern Europe. Custom engineering is cheap there and high quality. IP protection is a problem. One thing to do is to distribute the work to different manufacturers. For the design phase you are safer if you design your prototype in Europe or the US where international patent laws apply. I could give you more specific advise in a phone call, getting to know a bit better what you are trying to build.GF
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.