Born a sconie right on Lake Michigan, lived in Iowa for a handleful of years for college, then moved to Sota where I live currently. Software Engineer for 20+ years, Ham Radio Operator, lover of retro graming, old time radio and the outdoors.
Mastodon: jecxjo@mastodon.sdf.org
Not that a date in a file really is valid evidence, but the point is to define when the copyright occurs. If i come back and say “well i did that same thing before you did” them it would make your copyright invalid.
If you update then you add an additional date.
I’ve always been amazed when i get a new “seasoned” project manager and they try to really work on making all the tracking as efficient as possible so they have tons of metrics.
…and then nothing happens. We don’t look at projects and tasks and figure out which work would be best for which team members based on past experience. We don’t do any sort of optimization. We just track “velocity” and our estimates on release end up more dependent on how new the tech or the concept is (not knowing what we don’t know) than anything else.
I think its less about not understanding and more that these concepts only work in unrealistic scenarios that aren’t real. It’s the same with Agile. They never address the actual issue and try to work around them which never works.
I, as one of the ten people on the planet who writes awk scripts, noticed the most powerful text processing tool is missing.
Warsow / warfork
You don’t have to actually do a real project. It’s more about doing a task that requires you to create outside the hand holding.
After 15 years of OS and embedded systems development I learned web dev by creating a SaaS for my HOA’s property manager to communicate with tenants. Node, React, MongoDB, docker, iOS and Android apps. Did the project look good? Nope. Did I have to dig into manuals and debug for weeks, yep. But I easily stepped into a new role in an industry I had never worked in because I really learned the tech stack. Actually using the app wasn’t necessary, just that I actually had to create things requiring me to design around the technology I was learning.
Pick a problem in your life and solve it. Doesn’t need to become something you sell or publish or even use after you’re done learning. But the point is to actually use your skills.
I’m saying that the work they would be doing in two days isn’t the same as solving an actual problem. The way to really learn a language/framework/library is to actually use it in a real project. You run into pitfalls, you get compile errors and have to figure out how to debug in said tech, you find out how extentions to the tech work so you can create your own. Making a Todo Front End isn’t going to cover the vast majority of the stuff I’d expect one to know or experience when you say you “know” a language/framework/library/etc.
Oh i know, was joking mostly. At that point i had half a dozen languages under my belt and for tutoring purposes i was good to go.
To be fair, i did cover the Fortran 95 spec in a weekend, but i was motivated to tutor aerospace engineerings as there were far more females there than in Electrical Engineering and Computer Science.
Because anyone worth their salt knows that the superficial hello world example covers the tip of the iceberg. So to say you learned it in two days means you either don’t get that you barely scratched the surface or you dont get what other developers really need when they hire someone with knowledge in a specific framework.
The problem was that my boss was a title hopper and needed to fill his old position and he did it with yes men who wouldn’t stand up for anything. Meant that these yes men were also not the greatest at doing the rest of the job either.
They were expecting me to just do Hero Engineering by not objecting, put in more time and fill on the gap when theu couldn’t do their job. Was the first time in 20 years i ever was reprimanded, been praised at everything else I’ve done. So i knew at that point this was just a toxic place to work.
We aren’t talking about a bug, new feature stories. No screen shots, no identifieres to get me closer to a solution.
For example one of my stories had the following as the total amount of text for the entire ticket: “Add parser for new message type.”
Add the parser where? What is the new message type? Is this for a test tool or the project itself? Unit test framework? In a library or in the project code? We were working on two protocols and one protocol had a high level and low level message structure so i literally had 3 possibilities.
And when i asked my boss what the ticket was about i was told that i should do some investigation and fill in the ticket myself. Wtf?!? When i then told my productivity was wanting i started looking for a new job.
The last place i worked at they started pushing the same type of cringe. What made it worse was the PM/BA wasnt actually writing stories. One sprint I had 4 stories with just titles and “TBD” on the description. His boss was mad that my productivity was low when i couldnt do the work they couldn’t describe.
Haha did the same thing years ago to make the code look like free flowing text.
The big difference here is there is already this “learning curve” about the whole fediverse that people were struggling with that many of us wrote blog posts and had toot chains we’d forward explaining how this universe works. Adding in links and screen shots and templates for how to submit a bug…
…I hate saying this but the vast majority of people are just lazy. It’s not a culture issue or not something too difficult. People like to complain and not put in effort to things. People expect others to do things for them and don’t get that free comes with a cost.
FOSS isn’t really that small, it’s just that most people don’t do any type of investigation into what they use for technology. Much of what you use may have a for-profit company in front of it but huge parts of their products are open source andnyou can directly influence the products by actually engaging the projects themselves.
When the last big Twitter migration to Mastodon occurred there were a lot new users complaining about things like documentation, bugs, etc. Old users and FLOSS supporters kept pushing the “its open source, write a doc or fill out a bug ticket” and evem included documentation on how to do those tasks.
Most people just continued to complain. /facepalm
Posted as a comment
Copied from Google for those who don’t want to deal with Google:
Dear all,
It is with a heavy heart that we have to inform you that Bram Moolenaar passed away on 3 August 2023. Bram was suffering from a medical condition that progressed quickly over the last few weeks.
Bram dedicated a large part of his life to VIM and he was very proud of the VIM community that you are all part of.
We as family are now arranging the funeral service of Bram which will take place in The Netherlands and will be held in the Dutch lanuage. The extact date, time and place are still to be determined. Should you wish to attend his funeral then please send a message to funer...@gmail.com. This email address can also be used to get in contact with the family regarding other matters, bearing in the mind the situation we are in right now as family.
With kind regards, The family of Bram Moolenaar
Of all the software i have used in my 40 years on this planet, ViM has been the one constant. It is the first thing I install on every computer I use. It’s the source of so much of my productivity as a developer. The way us ViM users interact with documents is very unique, something that is often mimicked in other tools and editors. So many of us owe a debt of gratitude to Bram and the countless developers who have contributed to such a life-changing project.
I just self host gitolite. I wrote a script for archiving tagged versions to zip files as well as an optional parameter to pipe code into a markdown file and convert that to HTML for code i wish to show people. Everything else I do through the cli and have no use for a fancy UI.