Working together, Matching Wants / Wishlists, Payments and 'occasioal' Exchanges...
The question that each individual should ask themselves before taking upon any task is why are they doing it?
Is it because they want to or is it because they have to.
As long as one finds individuals that want to do a specific job, then an exchange of services could work.
And this is the core concept behind open source projects or non-profits.
Individuals who have to do task are more prone to lose motivation and thereby might delay or in the worst case cancel the whole gig altogether. Thus a formal contract should still exist to catch such cases where states something in the lines of:
> If one does not provide the service as advertised, then this price is due.
Further one should put also a clause that manages the expectations. This in the long run won't discourage the employer to quit potential further gigs.
The only benefit I see behind wish lists is that it could be an option to circumvent income tax.
@freeschool it all depends on what kind of pricing model one prefers.
I prefer the project plus optional service model.
Things to consider:
1. Who and how will it be hosted? Prefer with codeberg using two repos, one for development, and one for publishing.
2. How will it be themed: predefined or custom? Prefer predefined, since it is less work for me and customer can see results quite quickly. Some customers like predefined with customizations like different styling colors. For custom, a designer will need to be hired separately.
3. How many additional components will need to be made? Do all the components aka partials from the theme suffice, or do new components have to be integrated. This is the most work, since one will need to abstract component just enough so that the customer can add the different values for the variables without needing to deal with the underlying code.
Optional service: maintenance
The concept of git is just too much for the basic individual, thus one will have to maintain this step.
Next the abstraction of markdown is too difficult for many to understand, thus one will have to pattern match between documents and markdown.
Next the meta data of each markdown file might be too much on top of the abstraction of markdown to understand which patterns are acceptable and which ones are not, so more maintenance here.
In the end, unless the customer is willing to learn the services and technology, they will purchase the whole package.
Project: one time cost
Services: either monthly subscription or per entry
@eieio new way to communicate online
@freeschool still in development:
https://munich-rucking-crew.codeberg.page/
Main points were: ownership of content, speed, green development, accessibility, independence
Downside for me is that I will have more overhead in the long run.
@TheBreadmonkey thank you for your service! How else will your followers find comment worthy content?
@patrickworld isn't deep dish pizza technically tomato cake?
#DailyBloggingChallenge (326/365)
Do your #teeth hurt after drinking #CarbonatedDrink like #soda, #pop, #EnergyDrink or caffeinated ones like #BlackTea or #coffee?
Just use a straw!
This will help the liquid skip the teeth and/or reduce the time spent in the mouth.
#DailyBloggingChallenge (325/365)
The other day, I did a round of white #DressShirt #washing using the soak method and #detergent with #Oxi. These were soaked in a separate basin not to waste water in filling up a bathtub. To help sink the clothing, a 5lbs #FreeWeight was used.
After letting it soak for 6h, I realized that I made an irreversible mistake. The water plus detergent solution was so strong that it dissolved the coating of the free weights and created #rust spots throughout the clothing.
The only good thing is that it messed up the lesser important of the two shirts.
#DailyBloggingChallenge (324/365)
Learning about the directory architecture opened the gates of writing custom partials.
I previous knew of their existence depending on the specific theme and usually could avoid them by injecting custom #HTML.
Now that I have been hired to work on a professional site, especially after propagating why to use #hugo over #Wordpress, I shall use the framework to its standards and fullest capabilities.
#DailyBloggingChallenge (323/365)
One will learn that one will need to copy (usually) the whole file from the themes directory and mirror its directory structure onto the root level.
This can be quite a nuisance if one wants to change just one #CSS value.
#DailyBloggingChallenge (322/365)
The nice thing about #hugo is how quickly one can get a site up and running.
The tricky part of it is understanding its directory architecture. This can become more difficult if using a user predefined theme, especially if one wants to one's custom spin on nonexistent parameters.
#DailyBloggingChallenge (321/365)
When comparing the scraping method between Goruck's and Sandlot's page they differ quite significant.
On #Goruck one can use a simple #HTML parser and extract the data from a reusable #CSS class name.
On #Sandlot one has access to the response data as #JSON and needs to create a pattern/dictionary matcher.
#DailyBloggingChallenge (320/365)
Implementing ICS was quite easy after finding a functional library on #npmjs.
The difficulty was creating a parsing function that takes the already existing data format and put it into the #ical one. This means the new property `duration` was introduced using the same schema as provided from the ics library.
#DailyBloggingChallenge (319/365)
The original approach was to have a text field and reuse the list of clubs. This means one would have to use the `computed` functionality of #VueJS.
The downside of this option is that in the long run the UX would decline, since the list has the potential to be very long and thereby creating increased scrolling time.
#DailyBloggingChallenge (318/365)
Not just the amount of information should be considered, though also the style of #writing.
In the past, I wrote many AARs (After Action Reports). This is quite a simple task, since one is naturally looking back and writing in the past.
To challenge myself this time around, I chose the IAR (In Action Report) approach. The difficulty is that one is writing in the present tense while looking back onto the past. This makes the grammar so much more fun to deal with.
#DailyBloggingChallenge (317/365)
An interesting observation I am noticing while working on a long form article. The article in on an endurance event that lasted for 9 hours. Currently, I have spent at least 9 hours to get the first draft.
The fascinating part is that I will be spending more time #writing about the event than actually participating. This highlights how much information was introduced in those nine hours that it needs more hours to process it.
I am a strong proponent of leaving this planet better behind than when I arrived on it. Thus to get the most bang for a lifetime my key focus is #longevity which I attempt to achieve with #nutrition specifically #plantbased.
Longevity is good and all as long as you are not frail and weak. Ideally would be to die young at an old age. Thus I incorporate tactics from #biohacking and #primalfitness. Additionally I am an advocate of #wildcrafting, which is a super set of #herbalism.
Studied many fields of science like maths or statistics, though the constant was always computer science.
Currently working as a fullstack web developer, though prefer to call myself a #SoftwareCrafter.
The goal of my side projects is to practice #GreenDevelopement meaning to create mainly static websites. The way the internet was intended to be.
On the artistic side, to dub all content under the Creative Commons license. Thereby, ideally, only using tools and resources that are #FLOSS #OpenSource. #nobot