From b3332b33e529a853d2da6224b0a24e6bf102a930 Mon Sep 17 00:00:00 2001 From: Diane M Date: Fri, 2 Feb 2024 08:39:43 +0100 Subject: [PATCH] new article --- content/posts/feature-production.md | 65 +++++++++ public/index.xml | 53 ++++++- public/posts/index.xml | 211 ++++++---------------------- public/sitemap.xml | 30 +++- public/tags/index.xml | 22 ++- public/tags/untagged/index.xml | 33 ++++- 6 files changed, 237 insertions(+), 177 deletions(-) create mode 100644 content/posts/feature-production.md diff --git a/content/posts/feature-production.md b/content/posts/feature-production.md new file mode 100644 index 0000000..74730d8 --- /dev/null +++ b/content/posts/feature-production.md @@ -0,0 +1,65 @@ +--- +title: "Feature Production" +date: 2024-02-02T07:29:33+01:00 +draft: true +--- + +# My engineers output is slower than ever + +There is a catch that is never really explained in agile methodology, and is inherent to any software development lifecycle. + +It is always slowing down, one day or another, and *significantly* so. + +Your velocity will crash. Either your estimates will inflate, or the velocity will drop. Less and less features get out. + +We will cover here what is that phenomenon about and how to act upon it. + +## What deciders have to understand about it + +A product becomes increasingly complex as it develops. A product keep doing more and more different things, in a more and more robust way. + +This increasing level of demand on your output raises the bar for what is demanded for the developer to know before entering a coding session. + +The product context, the stregthened process, the increasing base of potential existing product interaction pitfals, the overall technical layers to know and to respect quality level on (logging, tests, architecture etc.) are as many increasing weights a developer must lift. + +This is not to be underestimated: this will lead to slower developer training, increasing number of mistakes in development flow, and even bore and burn outs, who sporadingly show themselves in the dress of "We should have a project friday" a.k.a. dedicated time to start fresh without the mental strain to code on the main thing. + +The worst part? This is ineluctable. Development leads to having things developed already. No magic methodology can trick you away. No clever code architecture. No given process or management technique. + +However, there are some answers that are to be found to ease the pain. + +## Tips and tricks + +### Product + +Admit mistakes: simplify your product. Streamline the value from your software. If something stops bringing enough cash, cut it. + +There is a mirage that a feature cost is estimated by its dev time. This is fundamentally wrong. A feature keep costing after development, for all the bugfix, security maintenance and other costs are to be spent maintaining it afloat. The sheer existance in your codebase of something that isn't necessary, costs money. The product must remain as simple as it can possibly be. + +Shift paradigm: at a given team size, there is a finite number of features you can provide. Choose wisely. + +### Code + +There is nothing really new here, but code maintenance must be held at high standard. Good architecture must be well cut in blocks, that different people will be in charge of maintaining, to reduce the amount of knowledge that is necessary for one to know from the overall frame. + +The best engineers know and will have a plan for this. Be sure to have them, divide and conquer. + +### Time management + +A company should have a generous portion of their development time dedicated to tackling technical debt. That can be: architectural debt, data modeling changes, infrastructure. We're not even speaking about bugs, we're talking about things that do not impact anything at the functional level (except for a performance increase here and there). 1/4 - 1/3rd of the time can be good amounts, and the earlier you do it, the better you have returns for it. + +This sounds like a cash burn to some non-technical deciders, but amazingly enough, once you start asking the team, digging for things that can be improved at the same perimeter, you usually find a ton of stuff. You will make your developers empowered and valued as you will enable them to ideate and carry on things that can save a ton in the long run. + +Having less time for features also means you might have to choose them with a little more recoil. + +### HR + +Because when a knowledgeable developer goes, their knowledge is lost, it's important to manage turnover. That doesn't necessarily mean throwing a lot of cash, but that means paying decently. Once that is sorted, the company should strive to offer good working conditions, and proactively remove anything that can be toxic in the environement, like micromanagement, harrassment, bro culture etc. + +Interpersonal respect must be taken care of by everyone and managers have to be examplary. Frequent 1-on-1 will enable higher ups to keep in check with individually varying needs. + +## Final words + +I wrote this article frustrated by the idea that many methodology conveys that producing features is similar to a factory output. Nothing could be more wrong. A software is a shared ownership living entity, that each and everyone have responsibility in how they impact it, and business goals are only one part of that input. A software with "more features" isn't a better software: many softwares are, on the contrary, praised for *being the best at what they do*. + +I believe as a SaaS company, this should be the common, unifying goal, rather than measuring an output. And perhaps, if your output is slowed down, it means you work for the quality of the output more than you were before? \ No newline at end of file diff --git a/public/index.xml b/public/index.xml index f503667..1550391 100644 --- a/public/index.xml +++ b/public/index.xml @@ -1,5 +1,52 @@ -Diane M's bloghttps://princess-entrapta.github.io/blog/Recent content on Diane M's blogHugo -- gohugo.ioen-usThis work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.Wed, 01 Nov 2023 19:31:16 +0100Developers Work From Homehttps://princess-entrapta.github.io/blog/posts/work-from-home/Wed, 01 Nov 2023 19:31:16 +0100https://princess-entrapta.github.io/blog/posts/work-from-home/After presenting developers work from home data, I will present key opportunity and challenges that arise from it. I will then conclude with personal opinion and recommendation regarding work for home for developers. + + + + Diane M's blog + https://example.com/ + Recent content on Diane M's blog + Hugo -- gohugo.io + en-us + This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License. + Wed, 01 Nov 2023 19:31:16 +0100 + + Developers Work From Home + https://example.com/posts/work-from-home/ + Wed, 01 Nov 2023 19:31:16 +0100 + + https://example.com/posts/work-from-home/ + After presenting developers work from home data, I will present key opportunity and challenges that arise from it. I will then conclude with personal opinion and recommendation regarding work for home for developers. Key data Stack overflow 2023 developer survey disclosed that: -42% respondants developers work in totally remote environment 42% in hybrid environment, mixing in office and remote work 16% in fully in-office. Self-employed developers work remotely for 70% of them.Green Ithttps://princess-entrapta.github.io/blog/posts/green-it/Fri, 27 Oct 2023 18:53:49 +0200https://princess-entrapta.github.io/blog/posts/green-it/Some figures about IT and the environment Electronic devices and other IT related activity represent 4% of the total global carbon footprint, a figure that is growing every year due to sector growth. If the proportion may look small, it actually is important regarding other industry sectors; automobile sector, known for its pollution side effects, in its whole is for example estimated weighting roughly 6 to 9% of global carbon emissions.Dockerfile for small Rust images (with dependency build caching)https://princess-entrapta.github.io/blog/posts/build-rust-dockerfile/Wed, 25 Oct 2023 12:56:00 +0200https://princess-entrapta.github.io/blog/posts/build-rust-dockerfile/Introduction After reading multiple tutorials for building docker images and optimize them, I compiled an optimized Dockerfile that can: +42% respondants developers work in totally remote environment 42% in hybrid environment, mixing in office and remote work 16% in fully in-office. Self-employed developers work remotely for 70% of them. + + + + Green It + https://example.com/posts/green-it/ + Fri, 27 Oct 2023 18:53:49 +0200 + + https://example.com/posts/green-it/ + Some figures about IT and the environment Electronic devices and other IT related activity represent 4% of the total global carbon footprint, a figure that is growing every year due to sector growth. If the proportion may look small, it actually is important regarding other industry sectors; automobile sector, known for its pollution side effects, in its whole is for example estimated weighting roughly 6 to 9% of global carbon emissions. + + + + Dockerfile for small Rust images (with dependency build caching) + https://example.com/posts/build-rust-dockerfile/ + Wed, 25 Oct 2023 12:56:00 +0200 + + https://example.com/posts/build-rust-dockerfile/ + Introduction After reading multiple tutorials for building docker images and optimize them, I compiled an optimized Dockerfile that can: Have final images that are small, in the 50MB range Benefit from docker caching, allowing to have build times under 10s if you don’t change dependencies We will assume here you start with a project my_app you already have or have created with cargo new. -Setting up We use this docker file.About Mehttps://princess-entrapta.github.io/blog/about-me/Wed, 25 Oct 2023 00:00:00 +0000https://princess-entrapta.github.io/blog/about-me/Coming soon \ No newline at end of file +Setting up We use this docker file. + + + + About Me + https://example.com/about-me/ + Wed, 25 Oct 2023 00:00:00 +0000 + + https://example.com/about-me/ + Coming soon + + + + diff --git a/public/posts/index.xml b/public/posts/index.xml index a3fbf68..7989afe 100644 --- a/public/posts/index.xml +++ b/public/posts/index.xml @@ -1,172 +1,43 @@ -Posts on Diane M's bloghttps://princess-entrapta.github.io/blog/posts/Recent content in Posts on Diane M's blogHugo -- gohugo.ioen-usThis work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.Wed, 01 Nov 2023 19:31:16 +0100Developers Work From Homehttps://princess-entrapta.github.io/blog/posts/work-from-home/Wed, 01 Nov 2023 19:31:16 +0100https://princess-entrapta.github.io/blog/posts/work-from-home/After presenting developers work from home data, I will present key opportunity and challenges that arise from it. I will then conclude with personal opinion and recommendation regarding work for home for developers. + + + + Posts on Diane M's blog + https://example.com/posts/ + Recent content in Posts on Diane M's blog + Hugo -- gohugo.io + en-us + This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License. + Wed, 01 Nov 2023 19:31:16 +0100 + + Developers Work From Home + https://example.com/posts/work-from-home/ + Wed, 01 Nov 2023 19:31:16 +0100 + + https://example.com/posts/work-from-home/ + After presenting developers work from home data, I will present key opportunity and challenges that arise from it. I will then conclude with personal opinion and recommendation regarding work for home for developers. Key data Stack overflow 2023 developer survey disclosed that: -42% respondants developers work in totally remote environment 42% in hybrid environment, mixing in office and remote work 16% in fully in-office. Self-employed developers work remotely for 70% of them.After presenting developers work from home data, I will present key opportunity and challenges that arise from it. -I will then conclude with personal opinion and recommendation regarding work for home for developers.

-

Key data

-

Stack overflow 2023 developer survey disclosed that:

-
    -
  • 42% respondants developers work in totally remote environment
    • -
  • 42% in hybrid environment, mixing in office and remote work
    • -
  • 16% in fully in-office.
    • -
  • Self-employed developers work remotely for 70% of them.
    • -
-

Because of collection source, the sample could be skewed towards more remote than in office sample, but remain one trustable labor source worldwide.

-

An other survey on developers (terminal.io) found 80% say they they want to work remotely at least 80% of the time. Crossing data means around 40% of developers are dissatisfied with the remote policy of their company.

-

Reasons invoked to prefer remote include productivity and focus, saving stress, and saving time & money related no longer having to having to commute, -while mentionned advantages to work in office include better communication, bonding, and better team efficiency.

-

Adapting to the employes

-

Choosing a model

-

When it comes to organizing the same team of developers, the 3 work styles (in-office, hybrid and fully remote) are challenging to make coexist. Based on the company choice, it will face different challenges.

-

Challenges and optimization

-

To make a comfortable work environment, any organization should:

-
    -
  • Providing reasonable commute time
    • -
  • Enable means of quality communication
    • -
  • Offer comfortable space and quiet
    • -
  • Lack distractions
    • -
-

These can be challenging to provide for both remote and in office organisation, for different reasons.

-

In office organization

-

In office organization will face a lot of recruitment challenges. Their recruitment area is more limited, and developers who are willing to engage durably in them are fewer.

-

However, they can work on their retention by providing to employees a high level of working confort. This includes, for people who would be inclined to prefer remote:

-
    -
  • A central positionning regarding transportation of the team.
    • -
  • Sufficient space and separation to avoid lack of focus related to overhearing discussions.
    • -
  • Formal and informal discussion spaces away from the screen.
    • -
-

Remote organization

-

Remote organization is highly desirable for both employees and employers, because it allows broader area employment, it removes necessity of large offices, it removes necessity to commute, and cut down distractions; without any possible doubt, in terms of efficiency remote is king.

-

However, full remote is not suited to all, and transitionning to it is difficult for employers. Some employees can have unfriendly home environments, prefer the office, and if they have been hired on that premise, disagree with change.

-

Finally, while efficient, it may be ill suited for the purpose of bonding between employees, for a set proportion of them who prefer in-person interaction by a higher margin.

-

To counterbalance this, an efficient remote organization should ideally:

-
    -
  • Have in-person events. These events should include as little actual development as possible, and be more of a planned occasion to meet, plan in team, and have informal discussion.
    • -
  • Propose to compensate for working in nomad offices such as coworking environments.
    • -
-

Hybrid organization

-

A hybrid workplace will be variably occupied, and both formal and informal meeting may need some level of effort to include remote workers: in office calls, remote meetings, and text retranscriptions.

-

While this compromise can be tempting, it is important to care that employees can variably adapt to this organization, as they would need to transit with their equipment frequently, and might poorly coordinate their office days with the people they wanted to meet in person.

-

Efficient organizations can include either a calendar to book the office, or an office large enough for everyone to come at the same time.

-

They should also include working devices to make remote meetings such as meeting rooms with included quality audio i/o devices.

-

Why I believe in remote

-

Work from home and in office don’t have to win one over another. Both offers probably should coexist to satisfy a large panel of opinions.

-

However, as a decider one can reap stronger benefits from a work from home company model in the current state of the market.

-

While this require some enagement to make these organizations work fluently, we saw how clever management can partly offset remote challenges.

-

As a remote enthusiast, I cannot wait to see more company daring to embrace this model, as it is, to my own standpoint, a great opportunity both for businesses and employees.

-]]>Green Ithttps://princess-entrapta.github.io/blog/posts/green-it/Fri, 27 Oct 2023 18:53:49 +0200https://princess-entrapta.github.io/blog/posts/green-it/Some figures about IT and the environment Electronic devices and other IT related activity represent 4% of the total global carbon footprint, a figure that is growing every year due to sector growth. If the proportion may look small, it actually is important regarding other industry sectors; automobile sector, known for its pollution side effects, in its whole is for example estimated weighting roughly 6 to 9% of global carbon emissions.Some figures about IT and the environment -
    -
  • Electronic devices and other IT related activity represent 4% of the total global carbon footprint, a figure that is growing every year due to sector growth.
    • -
  • If the proportion may look small, it actually is important regarding other industry sectors; automobile sector, known for its pollution side effects, in its whole is for example estimated weighting roughly 6 to 9% of global carbon emissions. The entiere plane fleet is 2%.
    • -
  • A computer (laptop or desktop) will during the course of its life emit a bit less than 100kg of CO2 eq. per year, cost which is between 70-90% manufacturing carbon footprint and the remaining in electricity costs.
    • -
  • Among e-waste, monitors represent a significant volume. E-waste is difficult to recycle, and may under some circumstances become an environmental hazard.
    • -
-

Misconceptions around green IT

-

Latest model efficiency compensates for replacement

-

This is trivially wrong based on the above facts. Even 10 years ago, e-devices were for most part energetically sober. However, their manufacturing and disposal are polluting processes. -Besides, unlike it could be the case for a car, having more efficiency at hand does not necessarily result in less consumption. If anything, more powerful model create new uses, creating more consumption.

-

Some programming languages are less green than others

-

Some people pointed out because Python is several dozen times less efficient than C, it is dozen times less green than C. While not completely wrong, this is simplistic.

-

It’s only measuring runtime power consumption. Programs written in Python could take less time to write, thus possibly compensating. -Resources on server side are rarely optimised below a certain threshold, so if two programs take one same vps instance, they are polluting the same. -Finally, providing services more efficiently power-wise might not decrease overall consuption for tech, if it drives price down it may in turn increase demand.

-

We need to sober up on emails

-

This is among all conceptions I heard one of the most strange. SMTP traffic is perhaps 1% of the world’s internet traffic. A mail is a few KB. A single video on yt will be thousands of times more costy. -Yet, this is a misconception I often have seen vehiculed by some corporations, encouraging their employees to “green gestures” such as deleting their email. But that’s misleading, as its not even a drop in the ocean

-

Positively changing actions

-

Over the last few years, there have been a massive shift in our usage of digital devices.

-
    -
  • We use videos a ton, for everything
    • -
  • We spend a lot more time gaming
    • -
  • We get helped more and more by new content generators and smart assistants
    • -
-

These 3 usages are heavily impacting traffic and waste, each in a different manner:

-
    -
  • Netflix, YouTube, Tiktok, Amazon prime, Disney +, cumulate almost 40% of the global internet traffic, with massive repercussions on the usage of servers, routers etc. since video content is heavy
    • -
  • Gaming represent a fair portion of traffic, but more importantly have become an increasingly common reason to renew hardware for more powerful versions
    • -
  • Content generators are sober on their apparent side, but bots like ChatGpt requires absolutely massive backend infrastructure to ingest and process a lot of data. No less than 240 CO2 tons (500 computer manufacturing equivalent) are thrown every year in the training of the artificial intelligence. And this is becoming ordinary business…
    • -
-

Conclusion

-

Concerns about electronic pollution is legitimate. But it would be foolish to believe we could stop it by writing more efficient programs. We however can take responsibility in reducing the entertainment usage of the digital tool, and use data-hungry AI models with measure.

-]]>Dockerfile for small Rust images (with dependency build caching)https://princess-entrapta.github.io/blog/posts/build-rust-dockerfile/Wed, 25 Oct 2023 12:56:00 +0200https://princess-entrapta.github.io/blog/posts/build-rust-dockerfile/Introduction After reading multiple tutorials for building docker images and optimize them, I compiled an optimized Dockerfile that can: +42% respondants developers work in totally remote environment 42% in hybrid environment, mixing in office and remote work 16% in fully in-office. Self-employed developers work remotely for 70% of them. + + + + Green It + https://example.com/posts/green-it/ + Fri, 27 Oct 2023 18:53:49 +0200 + + https://example.com/posts/green-it/ + Some figures about IT and the environment Electronic devices and other IT related activity represent 4% of the total global carbon footprint, a figure that is growing every year due to sector growth. If the proportion may look small, it actually is important regarding other industry sectors; automobile sector, known for its pollution side effects, in its whole is for example estimated weighting roughly 6 to 9% of global carbon emissions. + + + + Dockerfile for small Rust images (with dependency build caching) + https://example.com/posts/build-rust-dockerfile/ + Wed, 25 Oct 2023 12:56:00 +0200 + + https://example.com/posts/build-rust-dockerfile/ + Introduction After reading multiple tutorials for building docker images and optimize them, I compiled an optimized Dockerfile that can: Have final images that are small, in the 50MB range Benefit from docker caching, allowing to have build times under 10s if you don’t change dependencies We will assume here you start with a project my_app you already have or have created with cargo new. -Setting up We use this docker file.Introduction -

After reading multiple tutorials for building docker images and optimize them, I compiled an optimized Dockerfile that can:

-
    -
  • Have final images that are small, in the 50MB range
    • -
  • Benefit from docker caching, allowing to have build times under 10s if you don’t change dependencies
    • -
-

We will assume here you start with a project my_app you already have or have created with cargo new.

-

Setting up

-

We use this docker file. This technique is called a multi-stage build. When docker builds with docker build or docker compose build, it creates two successive images:

-
    -
  • One that serve to create the binary
    • -
  • One that will execute the binary without the build environment
    • -
-

The second one can be minimized by removing unecessary system components that are already bundled in the produced binary.

-
## BUILDER IMAGE
-FROM rust:1.73 as builder
-
-WORKDIR /usr/app
-RUN rustup target add x86_64-unknown-linux-musl
-RUN apt update && apt install -y musl-tools musl-dev
-RUN update-ca-certificates
-
-WORKDIR /usr/app/api_gateway
-
-RUN adduser \
-    --disabled-password \
-    --gecos "" \
-    --home "/nonexistent" \
-    --shell "/sbin/nologin" \
-    --no-create-home \
-    --uid 10001 \
-    userland
-
-COPY ./Cargo.toml ./Cargo.toml
-RUN mkdir src && echo "fn main(){}" > ./src/main.rs
-# Build the dependencies. This is the longest part and we don´t want
-# to repeat it if there is no dependency change,
-# which is why there is no copy or volume for sources at this point
-RUN cargo build --target x86_64-unknown-linux-musl --release
-COPY ./src ./src
-
-# 5. Build for release.
-RUN cargo build --target x86_64-unknown-linux-musl --release
-## EXECUTOR
-FROM alpine
-# You can include a healthcheck here, for demons and network-based services.
-# For http checks, don't forget curl is not readily available on alpine
-
-# HEALTHCHECK --interval=30s --timeout=30s --start-period=5s --retries=3 CMD [ "curl --fail http://localhost:8000/health" ]
-# RUN apk add curl
-RUN apk add libc6-compat
-
-WORKDIR /opt
-COPY --from=builder /etc/passwd /etc/passwd
-COPY --from=builder /etc/group /etc/group
-COPY --from=builder /usr/app/my_app/target/x86_64-unknown-linux-musl/release/my_app ./
-
-RUN chown userland:userland ./my_app
-
-CMD ["/usr/app/my_app"]
-

Alpine doesn’t natively provide glibc or libssl. For this reason, we will need some additions in the Cargo.toml file.

-

At end of file, below your dependencies, add the following section:

-
[target.'cfg(all(target_env = "musl", target_pointer_width = "64"))'.dependencies.jemallocator]
-version = "0.3"
-

You can learn more about what is jemalloc here

-

If you use things that are dependent of ssl, such as reqwest, you might also need to tweak the dependency to include rust-tls:

-
reqwest = {version = "0.11", default-features = false, features = ["json", "rustls-tls"] }
-

Running

-

Try to docker build your image. If it is successful, try to docker run the obtained container. It should execute your binary.

-

You notice your first docker build was probably long, several minutes long perhaps.

-

Try to modify your sources, then docker build again. You should notice the build to be significantly faster.

-

Use docker images and inspect image size. Smaller images are faster to push and pull over network, they also cost less to store.

-

Conclusion

-

We learned to make a multi-stage build to produce small docker images for Rust, and use the best of docker caching to avoid a costy rebuild -of dependencies at every source change.

-

Thanks to / further reading

- -]]> \ No newline at end of file +Setting up We use this docker file. + + + + diff --git a/public/sitemap.xml b/public/sitemap.xml index f03f2dd..9cad89d 100644 --- a/public/sitemap.xml +++ b/public/sitemap.xml @@ -1 +1,29 @@ -https://princess-entrapta.github.io/blog/posts/work-from-home/2023-11-01T19:31:16+01:00https://princess-entrapta.github.io/blog/2023-11-01T19:31:16+01:00https://princess-entrapta.github.io/blog/posts/2023-11-01T19:31:16+01:00https://princess-entrapta.github.io/blog/tags/2023-11-01T19:31:16+01:00https://princess-entrapta.github.io/blog/tags/untagged/2023-11-01T19:31:16+01:00https://princess-entrapta.github.io/blog/posts/green-it/2023-10-27T18:53:49+02:00https://princess-entrapta.github.io/blog/posts/build-rust-dockerfile/2023-10-25T12:56:00+02:00https://princess-entrapta.github.io/blog/about-me/2023-10-25T00:00:00+00:00 \ No newline at end of file + + + + https://example.com/posts/work-from-home/ + 2023-11-01T19:31:16+01:00 + + https://example.com/ + 2023-11-01T19:31:16+01:00 + + https://example.com/posts/ + 2023-11-01T19:31:16+01:00 + + https://example.com/tags/ + 2023-11-01T19:31:16+01:00 + + https://example.com/tags/untagged/ + 2023-11-01T19:31:16+01:00 + + https://example.com/posts/green-it/ + 2023-10-27T18:53:49+02:00 + + https://example.com/posts/build-rust-dockerfile/ + 2023-10-25T12:56:00+02:00 + + https://example.com/about-me/ + 2023-10-25T00:00:00+00:00 + + diff --git a/public/tags/index.xml b/public/tags/index.xml index 2bf61b9..8143f74 100644 --- a/public/tags/index.xml +++ b/public/tags/index.xml @@ -1 +1,21 @@ -Tags on Diane M's bloghttps://princess-entrapta.github.io/blog/tags/Recent content in Tags on Diane M's blogHugo -- gohugo.ioen-usThis work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.Wed, 01 Nov 2023 19:31:16 +0100untaggedhttps://princess-entrapta.github.io/blog/tags/untagged/Wed, 01 Nov 2023 19:31:16 +0100https://princess-entrapta.github.io/blog/tags/untagged/ \ No newline at end of file + + + + Tags on Diane M's blog + https://example.com/tags/ + Recent content in Tags on Diane M's blog + Hugo -- gohugo.io + en-us + This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License. + Wed, 01 Nov 2023 19:31:16 +0100 + + untagged + https://example.com/tags/untagged/ + Wed, 01 Nov 2023 19:31:16 +0100 + + https://example.com/tags/untagged/ + + + + + diff --git a/public/tags/untagged/index.xml b/public/tags/untagged/index.xml index c0325be..dbf6a46 100644 --- a/public/tags/untagged/index.xml +++ b/public/tags/untagged/index.xml @@ -1,3 +1,32 @@ -untagged on Diane M's bloghttps://princess-entrapta.github.io/blog/tags/untagged/Recent content in untagged on Diane M's blogHugo -- gohugo.ioen-usThis work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.Wed, 01 Nov 2023 19:31:16 +0100Developers Work From Homehttps://princess-entrapta.github.io/blog/posts/work-from-home/Wed, 01 Nov 2023 19:31:16 +0100https://princess-entrapta.github.io/blog/posts/work-from-home/After presenting developers work from home data, I will present key opportunity and challenges that arise from it. I will then conclude with personal opinion and recommendation regarding work for home for developers. + + + + untagged on Diane M's blog + https://example.com/tags/untagged/ + Recent content in untagged on Diane M's blog + Hugo -- gohugo.io + en-us + This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License. + Wed, 01 Nov 2023 19:31:16 +0100 + + Developers Work From Home + https://example.com/posts/work-from-home/ + Wed, 01 Nov 2023 19:31:16 +0100 + + https://example.com/posts/work-from-home/ + After presenting developers work from home data, I will present key opportunity and challenges that arise from it. I will then conclude with personal opinion and recommendation regarding work for home for developers. Key data Stack overflow 2023 developer survey disclosed that: -42% respondants developers work in totally remote environment 42% in hybrid environment, mixing in office and remote work 16% in fully in-office. Self-employed developers work remotely for 70% of them.Green Ithttps://princess-entrapta.github.io/blog/posts/green-it/Fri, 27 Oct 2023 18:53:49 +0200https://princess-entrapta.github.io/blog/posts/green-it/Some figures about IT and the environment Electronic devices and other IT related activity represent 4% of the total global carbon footprint, a figure that is growing every year due to sector growth. If the proportion may look small, it actually is important regarding other industry sectors; automobile sector, known for its pollution side effects, in its whole is for example estimated weighting roughly 6 to 9% of global carbon emissions. \ No newline at end of file +42% respondants developers work in totally remote environment 42% in hybrid environment, mixing in office and remote work 16% in fully in-office. Self-employed developers work remotely for 70% of them. + + + + Green It + https://example.com/posts/green-it/ + Fri, 27 Oct 2023 18:53:49 +0200 + + https://example.com/posts/green-it/ + Some figures about IT and the environment Electronic devices and other IT related activity represent 4% of the total global carbon footprint, a figure that is growing every year due to sector growth. If the proportion may look small, it actually is important regarding other industry sectors; automobile sector, known for its pollution side effects, in its whole is for example estimated weighting roughly 6 to 9% of global carbon emissions. + + + +