2,390 karma · joined March 7, 2011
1. Expecting employees to support a project like this and do their regular day jobs. They can't. One will suffer, probably the one that is new and unfamiliar. This will frustrate the team working on the project (whether it's in house, freelancer or contract firm).
You can hire some new people first and train them up in a short time to take simple tasks off longer term employees plates so they can spend some percentage of their time supporting the project. Don't hire new people to support the project, they don't understand your business well enough. This is a cost of doing this type of project that is often ignored. And don't allocate something small like 10% of employees time. It should be at least 50%.
2. Expecting the project team to get all the requirements. Understand, in detail, what you need to build. This is not the time for agile. You have a known system that you want to replace. You aren't discovering a new application space. You can run the project with sprints, agile rituals etc. But don't do requirements throughout the project. Get them up front so the team knows what they are building and can architect it appropriately. This is a topic that I could write pages about but you will wish you had better specified requirements no matter how well you do them. You can carve out a small piece of the application at first to limit the scope but that piece needs full reqs.
3. Get something done and in the hands of your users now. I like to start with a checklist of a process. Replace one item on that checklist. Repeat.
login to system
click shipping
fill in manifest -> identified as the piece to replace.
check schedule on calendar tab
becomes login to system
click shipping
fill in manifest
login to new system
export manifest data
import into new system
check schedule on calendar tab
4. Setup your development, testing and production environments and keep them in sync.He has just heard from one of his mid level managers that things were blowing up and complained to our leadership which resulted in the meeting.
We were a pretty good company for doing contract work. Admittedly, we rarely made it past the"make it work" part of "Make it work. Make it right. Make it fast" but that's the nature of contract development.
Our biggest mistake on that was relying on them to PM their own projects.
They assumed because they knew how to do Big infrastructure projects that they could handle software and technology projects too. Things only started to get better when we basically embedded our own PMs in their teams.
Completely different example I encountered recently. A bike tech told me the highest end components need constant adjustment and maintenance since tey are made of such lightweight materials. Totally fine if you've got a dedicated maintenance tech on your racing team. Pain in the ass if you're a weekend warrior.
I struggle to have a good routine but spontaneity happens more often when I do.
If I go to the gym at 5:30 and do chores at 7 and go to work at 8 and eat lunch at noon and read at 6 and eat dinner at 7 and work on personal projects at 8 and go to bed at 10:30 then if something comes up I can say "I have an hour at lunch, lets meet" Or "I will skip my personal projects today and go to so and so's house"
If I'm just constantly chaotic then I'm always feeling harried and like I don't have time for anything. And even if I do make time for something spontaneous, then I'm feeling like I'm stealing time from myself even though I didn't really have anything planned during that time anyways.
Also 10x work is a silly idea to me. Progress happens in almost all areas because of consistency. Research, fitness, home life, relationships, work. They grow or produce or increase because you do them regularly not because you had some magical insight and suddenly need to disappear into a hole for a week to work on it.
His section on breaking routine feels like it completely misses the point.
"Serendipity loves randomness and hates routine"
There's also a saying that luck favors the prepared.
Rarely have a read a piece that is mostly well-written that resonates so poorly with me. It's like every insight he has is the opposite of my lived experience.
If you want someone to DO something you just need to show that it COULD fill a gap in some other part of their life. If it's addictive as well then they don't need to experiment for long before it's a solid part of their life.
Getting someone to stop plays off loss aversion and sunk cost.
Again maybe I've been lucky but honesty has worked well for me.
I did say that we would have to pay the piper eventually and that this rushed timeline would mean we would miss things and that it was only possible if we had everything in place to do the development work. Things like access, correct data, properly setup environment etc.
Of course we started development and had none of those things. I did get it out on time according to my shortened estimated. But then they discover that they absolutely do need some fixes and that the assumptions the dev team had to make because we didn't have real data were wrong so the whole thing is delayed by about as much time as the original estimate but there's a whole bunch of hand-wringing and people thrashing about because of "slipped timelines".
And I knew this going into it. No one ever hears "But we will have problems I just don't know what they will be" They just hear "I can get it to you in 3 weeks"
> The core misconception here seems to be the idea that there is such a thing as a honest for-profit corporation.
And I would say there's degrees. Even if all companies eventually slouch into a google-like organization, at least you can jump on the bandwagon until that happens and find another when it does. And maybe none of the wagons are headed to a strict privacy, user controlled data, and free-software utopia, but maybe not all of them are headed to Gomorrah.
I don't think we're going come up with a universal measuring stick to apply here though I'm sure some tech reporting outlets will try.
As a pithy illustration: If I'm trying to hit a tree with a ball and that tree just happens to be in between some goalposts and someone comes along and moves the goalpost, I can still hit my target even if I don't "make a goal". To a casual observer it might look like I'm playing the game and I am. But the game in my head is not the game in yours.
edit: I didn't have this in mind when starting this comment but maybe that's the deeper desire behind punk and other countercultural movements; the desire to play your own game. And maybe capitalism is the end of history in the sense that it has adapted to make it easy for people to play their own game and keeps pushing the edges of what would have been counter previously. Want to drop off the grid and make everything you use and consume with your own hands? There's a hundred youtube channels about that. If you want to conquer Rome, you're still gonna travel there on roads the Romans built.
This is not the current medical thought on early screenings for various cancers. It used to be and I was confused about it until very recently. Indeed the medical community is still wrestling with the issue of screening harms. The consensus is shifting that screening should only be done if there is an existing condition or symptom or family history.
https://www.cancer.gov/news-events/cancer-currents-blog/2022...
The real benefits of non-discriminatory practices is in diversity. Not HR sanctioned diversity but diversity of life as in nature. Monocultures of all types are fragile.
No one around here can figure it out either. I sit next to a guy at my coworking space who works on rural economic development. Just today he was putting together a report on some funding that was given to promote small businesses. He said they were supposed to present the report to the board but the program had done so poorly that they were just going to file the report and never bring it up again.
I really do think that the bigger issue is the housing. That and NIMBYism. We have the Wildflower Inn nearby that I used to vacation at with my family when I was a kid. It was run by a family for 40 years before it was sold a few years ago to a guy who had fallen in love with the area. I've ridden the lift with him a few times and chatted about all the problems he had trying to get approval for his development ideas.
The original owners did some beef farming on the land around the Inn. The new owner wanted to take the old barns and pastures and build a bunch of vacation cabins and camping spots with shared public spaces. The area was set back and not visible from the road. It would have been visible from the mountain biking trails but that's it. He got so much push back from the town and locals that he canceled the project.
Of course, he could just subdivide into the minimum rural 3 acre lots and the town could do nothing about it and then we'd have 40 individual driveways and large houses obstructing the view instead.
On the slopes, at my coworking space, and around the campfire in the Summer, the topic of how to make this little pocket of Northeast Vermont more economically viable is a topic that comes up often.
I'm starting to form an opinion that we shouldn't try to compete, at any level, with larger job centers. We lost a huge (per capita, it was never large in total dollar values) number of manufacturing jobs over the past 20 years. That's not coming back. Perhaps there's a niche for us, and other rural communities in creating a great place for people to live and work remotely. Funding co-working spaces and high speed internet is a lot easier than getting a manufacturer to move in given that we have a tiny labor market.
Bigger issues for getting any population growth is our perverse tax and housing regulations. Not going to go into them in depth here but we have a water protection act that adds 10-20% to any construction project near water and wetlands even if the area already has a lot of development. Besides making things more expensive, it also encourages sprawl since many communities are built near water but it's cheaper to build in the hills surrounding them away from wetlands. One of the only ways to make a real estate investment pay off up here is to buy a plot, subdivide into 3 acre lots, put in a road and electricity and sell housing lots. The hassle of dealing with Act 250 doesn't make it worth it to do the actual development and so you don't see it. The only developments in my area are either 40 years old or the aforementioned building lots.
We also have an aging and decrepit housing stock and the tax structure for capital gains strongly penalizes flipping houses which is an accelerator on updating housing inventory. Instead, housing investment, like many places, is solely in short term rental or buy and hold/rent.
Or, at least, I did until the m series processors came out and you could get a passively cooled laptop for a decent price.