My postings on LinkedIn have definitely had direct consequences in my professional life.
I consider them all good because ultimately if you get upset by the way I behave then that's probably going to be true if we work together also.
Sometimes people like to tell me that I'm very authentic and it's clear that I'm not trying to suck up to anyone, which they respect. Some people quietly retreat from me and I find out later that it's because I hurt their feelings inadvertently by shitting on AI or calling out web development as largely being inefficient in resources or something.
Love this response, and as some one who does perhaps a bit too much spending/wasting time on other types of social media, including here, I've made a conscious decision to post on LinkedIn more.
And it's such a difference. It forces me to slow down and think about a lot of things. The most important being: Is this even worth posting AT ALL?
And then, okay -- how can I say this in a future-proof way that both appeals to normies and tech folk like myself. I feel like I'll be doing better the more I post to places like that, and maybe less here?
There was a bit of a scandal at my employer some years back and IIRC it was kicked off by someone posting/boosting some really questionable stuff on LinkedIn.
What a great project idea, worth getting it clients. That's why I've build a platform for promoting young startapers to find theit niche audience. Give it a try and go to the moon!
I see in this story organisational boundaries between teams. Teams which don't have common coordination space (or used for something more __important__). Responsible people don't care enough to mitigate such deviations earlier
Yeah, we again have a solution (LLMs) in search of problems.
Proper approach to speeding things up would be to ask "What are the limiting factors which stops us from X, Y, Z".
--
This situation of management expecting things to become fast because of AI is "vibe management". Why to think, why to understand, why to talk to your people if you saw an excited presentation of the magic tool and the only thing you need to do is to adopt it?..
This is categorically not true. For almost all of my 30 years it’s been
1. Talk to the business, solve XYProblems, deal with organization complexity, learn the business and there needs.
2. Design the architecture not just “the code”, the code has to run on something.
3. Get the design approve and agree on the holy trinity - time/cost/budget
4. Do the implementation
5. Test it for the known requirements
6. Get stakeholder approval or probably go back to #4
7. Move it into production
8. Maintenance.
Out of all those, #4 is what I always considered the necessary grunt work and for the most part even before AI especially in enterprise development where most developers work has been being commoditized in over a decade. Even in BigTech and adjacent codez real gud will keep you as a mid level developer if you can’t handle the other steps and lead larger/more impactful/more ambiguous projects.
As far as #5 much of that can and should be done with automated tests that can be written by AI and should be reviewed. Of course you need humans for UI and UX testing
I see step 4 as interwoven with other steps. The implementation ideally takes into consideration the domain and while implementing, potentials for flexibility are potentially revealed, to be taken advantage of, "without programming ourselves into a corner". Implementation also is of course related to maintenance. Maintenance already needs to be taken into account. How easy is it to adapt the system we are building later?
This all happens while we are at the implementation stage and impacts all other aspects of the whole thing. It is a grunt work, but we need elite grunts, who see more than just the minimal requirements.
I’ve been going on about this in another thread in a separate post. That’s where modularity comes in. From code I write to teams (or multiple teams back in the day). I always enforce micro services. Not always separately deployable micro service, they could be separate packages with namespace/public/private accessibility.
Even if you do have not so good developers, they can ramp up quickly on one specific isolated service and you can contain the blast radius.
This isn’t a new idea. This was the entire “API mandate” that Bezos had in 2002. s3 alone is made up of 200+ micro services
What if they pay own bills (why is this even a subject of discussion?), increase supply (formally), but electricity prices still go up anyway? Just curios if scenario from my descrition even possible...
We are obviously dying. What's the point of doing anything in between now and the last moment? What goal of people who think that doing anything will make any impact?
--
Some people do that as a symbolic action. Some to keep own terms as much as they can. Some hope their actions will join others actions and will turn into a signal for decision makers. For others this action reduces the area of their exposure. Others believe in something and just follow their beliefs.
BTW following own set of beliefs is what you're (we all) doing here. You believe that surveillance is already happening and nothing can be done about it, that single action does not matter, that there are no other reasons for action other than direct visible impact, etc. Seems that you analyze others through own set of beliefs and it can not explain actions of others. This inability to explain others suggests that the whole model is flawed in some way. So what is the nature of your beliefs? Did you choose them or they were presented you without alternatives? What are alternatives then? Do these beliefs serve your interests or others?
Co-ownership of the hardware is a social not technical problem. Think of questions of trust, responsibility, who has power, who and how contributes, how decisions are made, etc, etc
Do you have examples of such occasions when the linkedin post was actually the cause?
reply