Header Image -

Monthly Archives

3 Articles

Obsidian Weekend

by dave

On my quest to start trying to figure out how to make good chess sets from rock, I want to try to make a black set from obsidian. I know of a few places to get obsidian, so T and I went out Friday evening to see if we could find pieces large enough to carve chess pieces. When we left, it was cold and windy. We drove through rain, hail, and snow. We got off the highway, and the skies were clear. Springtime is wonderful.

I had never driven to the obsidian pits from I-15 before… I had always come across from the west. But I had my paper maps, and a printout of what Google Maps thought the directions would be, and my maps on my phone. Only the paper maps were accurate. I looked at all 3 at every turn, and it got me close enough that when I was a couple miles away I was able to recognize the hills and just drive us up to the pit. T slept through all the stopping and gazing at maps.

Once we got there, T was pleased to see that I wasn’t kidding. It really was a pit of obsidian. Multiple pits, actually. But very few pieces were big enough to carve. We did find a few. But not enough for a chess set. We grabbed enough to make the pawns, and then drove a few more dirt roads in the area, looking for new places. We got out and explored, and did find more sites with obsidian. But nothing exciting. Places that might be of interest to people who haven’t collected obsidian before, or newer rock-hounders… but not really anything that I’d take the time to go back to.

There were also storms still moving about. We could see them moving around the valley, getting blown mostly south of us, but we did not want to get caught in one, so we decided just to keep driving, and head south to visit family.

Saturday, we decided to try a different site for obsidian. Much nicer day. No storms, not much wind. We drove  back up from the cousins’ house to our collecting area and tried a place I had not been before, which looked to be less picked over. At this site, the rocks were more scattered. It took some wandering and exploring, and the obsidian itself was less interesting. More plain black, very little with any coloration, and much of it didn’t even have much sheen to it. But despite those downsides, there were larger pieces. At first, we just found some fist-sized pieces, which we were happy with, because that was at least big enough to let us make the rest of the chess set. But then we found the piece that made the whole trip worth it…

Legal Tips from a Software Professional

by dave

I am not a lawyer. This is just my personal approach to the legal quagmires of working in the software world. But it does work for me. YMMV and make your own decisions. Also, the legal field is inherently adversarial. So this post approaches it that way, too — that you are in conflict with the people who are giving you contracts. But I also have good friends who are attorneys, and they have an uncanny ability to turn that adversarial switch on and off like a light. It is just part of their work. This is often just a game to them, and maybe that is why they do this job to begin with. So play it, but treat them like people, and don’t take things personally.

  1. When in doubt, seek professional help — The key to success is often knowing your own limitations. This is especially true in the legal arena. If you are unsure, ask. Better to get a clear answer than make a bad guess and get burned in the future.
  2. Read contracts carefully — The fine print does matter. But despite being complicated, legal language is still just English. Read it slowly, and carefully. Match up all the phrases in a sentence to be sure you understand which clause is attached to which, and it will make sense. The context of how it is applied in your jurisdiction and your specific circumstances is where you might need legal advice, but don’t buy into the myth that “legalese” is a different language. If you can structure a software app, you can break down a sentence in a contract and understand it.
  3. Contracts are two-sided — All contracts require “consideration”. This is a basic principle of contract law. If they do not give you something, they cannot demand anything of you.  Often, this means money in exchange for services or other agreements. The value of the two sides of the contract to not have to be equal, but there does have to be a give and take from both sides. If you don’t like a particular contract, but have a business need to make it happen anyway, this is the area in which to focus your negotiations — ask for more consideration. And if someone asks you to sign a contract where they do not give you anything… just say no. Even though it wouldn’t be a valid contract anyway, see the next point…
  4. Don’t follow the advice that “It is OK to sign a contract if it won’t hold up in court.” — I hear this more often than I would expect. There is this idea that if part of a contact won’t hold up in court, than you can just ignore it. This isn’t good thinking. First of all, you would have to fight it in court to get to that conclusion, which is both time-consuming and expensive. So if you believe that part of a contract is not enforceable, just ask it to be removed. Odds are, the lawyers will remove it if it really is that flimsy. And if they do not, well… you have something you need to negotiate with them.  Because litigation rarely ends up getting resolved at trial anymore anyway — it gets settled. So your potential future conflict is being negotiated right now. Settle the differences right now, not years down the road when this contract can be wielded against you, with legal fees and courts attached. Argue your points before signing.
  5. All contracts are negotiable — People say they won’t negotiate, but it is all about power. They want something from you, or you would not be in the position of looking at a contract in the first place. The question is how much they need you vs. how much you need them. If you are signing a contract for an entry level job with 100 other applicants, sure, maybe you have no room for negotiation. But if you are an expert in your field who get thrown a new contract after working at a company for years, asking to change your working relationship, and told sign it or lose your job, trust me — they’ll negotiate.
  6. Negotiation means compromise — I’ve heard it said, and repeated it myself, that you know a negotiation was fair when both sides walk away a little bit unhappy. You need to pick your battles in all areas of life, and contract negotiation is no different. Pick the areas that truly bother you, and fight for those. Don’t get bent out of shape over a couple points, and then nitpick everything in the contract just to be spiteful. Know what you care about. Know what you are willing to accept. Know what you are not willing to accept. And be willing to let the other side win some points.
  7. Negotiations are part of the interview process — Suppose you get a job offer, accept, and are just finishing out paperwork to start, when you find a few gotchas in an employment contract and negotiations get heated. In my mind, this is still the interview process. Not for whether they want you, but for whether you want to work for them. Are they being reasonable towards you in what they are asking in the contract? Are they kind in their approach to you in negotiations? Are they explaining why they need certain clauses, and working with you to find common ground to reach a resolution? Or are they just telling you to sign it, no questions asked? However they are treating you during this process, is that how you want to be treated by your employer?
  8. Do not be afraid to get sued — lawsuits are a mechanism of conflict resolution. If the lawsuit has no merit, just work the mechanisms to fight it, and counter-sue for legal costs. And take it as a compliment that you are doing enough things right that a competitor is threatened by you. Because if you run a successful business, someone eventually will sue you. Consider it a right of passage. Hire a good lawyer. Deal with it. And move on. Don’t run your business in fear of it, or you will stifle yourself. (And if their suit does have merit, take the hit, learn your lessons, recover, and still move on.) Also, lawsuits are the most expensive and painful way to resolve a conflict. If someone went this far, they really are just desperate to resolve a problem. You have an opportunity to seek a better resolution, and I’d take it.
  9. Do not let lawyers bully you — lawyers are not scary. They simply wield knowledge and threats as a weapon within their profession. But patience, research, reading, and your own attorney will solve all things. And nothing a lawyer sends you demands an immediate response. Look things over carefully. Get help if needed, and respond appropriately. Do not let corporate lawyers tell you that you must sign contracts to keep your job. In some places, that is not legal. (Utah, for example.) In others, it may be legal, but you still need to see if the contract is acceptable. No job is worth signing a bad contract. Not if you are a software professional, not in today’s market.
  10. Cease and Desist letters have no authority over you — They are a warning shot over your bow. They may be followed by a lawsuit. You may want to cease and desist, depending on circumstances. Or you may not. You are your own person, and the decision is yours. Just because someone got a degree, passed an exam, and sent you a letter, does not give them any authority to tell you what to do. Of course, the lawsuit that comes next, if they win it, could have authority. So be as bold as you want, but don’t be stupid.


Write like a 3rd Grader

by dave

The ability to communicate effectively has been a hot topic at work the past few months. Mostly because, frankly, people are doing it badly. Usually it is just minor stuff. Nothing to get too worked up about. But this past week, it was a train wreck. I’m sorely tempted to share details, but I’ll refrain. Instead, I’ll focus on the positive.

I need to first give credit where it is due — when I worked in Denver, I ran our internal collaboration systems, which included the intranet portals, and therefore I was involved whenever company-wide emails and announcements were made. Often, I simply posted them, but over time I started authoring some of them. And at first, I did it poorly. But our Communications Director would edit my announcements and emails, and help me become a better communicator, and by the time that job ended, I could just about write a corporate announcement that would pass her critiques without needing changes. It was a valuable experience, which may not have improve my writing on these blog posts, or even in my day-to-day emails, but does make me capable of keeping a team or an entire company informed of what is going on.

And it really is not rocket science. You need to write just like an elementary school student completing a writing assignment. Answer basic questions — What? When? Who? Why?

What is going on? When is it going to occur? Who will it affect? How will it impact me, my job, my team, etc? Why is it being done? And where do I get more information or ask questions? If your announcement answers those questions, it is good communications. If it does not, it is going to be a failure. It is really that simple.