Does it matter? If you don’t know enough can you figure it out? If you can’t figure it out, do you know who to ask? When things go sideways are you going to stop or keep pushing into it? The question isn’t how much you know, but how much desire and drive you have to learn to know.
Any piece of software has a set of configurations, toggles, and switches that make it come alive. The configuration is what makes the software work for your customer and makes it “their own, unique copy”. Four things a configuration should always have; A place to go and make the change, not forcing the customer to jump here, there, and everywhere. Settings that do what they are supposed to do. Be simple in their implementation, if…
Cars shift. If you’re driving standard, it’s a more pronounced shift, you need to initiate it, otherwise, the engine keeps revving. The persistent revving of the engine is the cue for you to know when to shift, you know by the sound that it can’t maintain its push unless you shift to a higher gear. Knowing when to shift, either yourself or your team is critical to growth and not as simple to determine as…
If you don’t have a team, get a team. A team can be anyone, random coworkers, related coworkers, family, or whatever. But get a team. And when you don’t know the answer. You ask the team, you leverage their skills and abilities in what you are trying to accomplish. That’s what they are there for, to help and support you. So get a team.
That’s the lesson I learned many years ago writing my first legit lines of code. It’s not yours, it’s not theirs, it’s ours. So if I get a bug and have to go in and fix it, no harm, no foul, I’m fixing our code. There is no ownership of code, there is no baby, and there is only our collective code being distributed to our customers. Yes you put a lot of effort into…