Hiring developers

Just wondering what the cost is to hire developers to create an MVP? Any insight on market rates, payment structure, and any other information would be greatly appreciated.

https://redd.it/11nw41a
@r_devops

Is there software to push my Dev server to my main server?


I have a Development game server and a main game server. I would like to find something like gitlab to track issues and push my development server changes to the main server. I need to be able to upload zip files and decompress them all while keeping track of what happens. Is there any software out there like gitlab thats is free and could accomplish this?

Thanks in advance

https://redd.it/11nrfer
@r_devops

Ultimate Guide to Pass DevOps Institute DOFD Exam

Secrets to Passing the DevOps Institute DOFD Certification on Your First Try

https://guides.co/g/dofd-exam-guide/259364

​

\#DevOpsFoundation #DOFD #DevOpsInstituteDevOpsFoundation #DevOpsInstitute #DevOpsInstituteDOFD #DevOpsInstituteCertifiedDevOpsFoundation #CertifiedDevOpsFoundation #DevOpsFoundationCertification #DevOpsFoundationExam #DevOpsInstituteDevOpsFoundationCertification #DevOpsInstituteDevOpsFoundationExam #DevOpsInstituteExam #DevOpsInstituteCertification #DevOpsInstituteDOFDExam #DevOpsInstituteDOFDCertification #DevOpsInstituteCertifiedDevOpsFoundationCertification #DevOpsInstituteCertifiedDevOpsFoundationExam #CertifiedDevOpsFoundationCertification #CertifiedDevOpsFoundationExam #DOFDCertification #DOFDExam #DOFDMockTest #DOFDPracticeExam #DOFDQuestions #DOFDSyllabus #DevOps

https://redd.it/11obrbf
@r_devops

The Impact of Developer Happiness on Productivity

Even in an era of unprecedented tech layoffs, most companies are still eager to find and retain top software developer talent. What’s more, many firms are discovering that they lack direct insight into their development teams’ needs and priorities. As a result, some of them are struggling to keep their developers happy and thus productive. A recent Zenhub report found, for the first time, a quantitative link between developer happiness and productivity, including what keeps developers in the same position instead of moving on to another job at the first sign of perceived trouble.

Software Development Happiness

The 2022 Software Developer Happiness report is based on a survey of 380 software professionals from a host of different organization types. In brief, the survey found that two of the biggest contributors to devs being unhappy in their roles were a lack of work/life balance and not working on what’s perceived as “quality work.”

Even with a looming recession and thousands of layoffs, there remains a dearth of senior software development talent. For more junior talent, there will be more available than in previous, pre-pandemic years. As companies strive to do more with less, they still require development teams to build their products and/or the applications that drive their business. Setting up more junior teams for success via collaboration and productivity tools will be key to navigating this new environment.

Given these findings, if organizations want to retain developer talent, they still need to make sure developers are working on meaningful projects and that they’re able to achieve that work in a way that balances the needs of the business with the needs of the individual.

An ideal example of this phenomenon is the developer tool ecosystem companies make available to their teams. While the growth of this ecosystem has been a net positive for developers, it has also created a lot of tool sprawl and significant integration challenges.

Less Time on Application Development

Stephen O’Grady, an analyst at RedMonk, an analyst firm focused explicitly on software developers, talked a lot about this through a term he coined called the “developer experience gap.” He is referring to developers spending more time integrating tools than working on application development or application code. That integration work comes at a real cost. It means developers are spending less time on application development, are having to work longer hours or do the integration work off the side of the desk.

The real bottom line to these survey results is that developers are happiest and stay at their jobs longer when empowered to focus on building code. This means spending less time interacting with management, attending meetings or resolving and integrating multiple solutions. The report’s results also emphasized the importance of work-life balance in encouraging developers to stay at their current job longer, while poor work-life balance accelerated the hunt for another job. These insights into developer retention are especially critical as, according to the report, 71% of developers haven’t decided how long they’ll stay with their current employer. The report also suggested that 33% of developers have stayed in a job longer than usual due to the pandemic, which could mean an increase in developer turnover when the pandemic comes to an end.

Another key finding is that collaboration challenges are viewed as the biggest impediment to developer productivity. Delays in feedback result in lost productivity; nearly 70% lose a minimum of three hours per week per developer and 75% spend at least an hour per week on reporting instead of writing code.

Finally, developers said their biggest priority is ensuring their software meets business demands, and most developers want high-performance productivity tools. In fact, 93% of developers believed these tools are critical to their success.

Increase Developer

Happiness

So what can team leads to alleviate these issues? For both team leads and more senior management, the biggest way to increase developer happiness is simply to let them focus on coding. Developers like to showcase their skills, so encouraging them to work on interesting and impactful projects that challenge their skill sets is a great way to boost morale. Ensuring an appropriate work-life balance and paying the developers competitively are the other two recommendations for improving developer retention.

Additionally, senior management should take another look at how they are compensating their teams. Financial compensation will always be a critical element, but we should expect to see companies shift their focus to programs and benefits that their employees truly need. Particularly given the somewhat chaotic year in 2022 and continuing in 2023, those in the technology industry will shift to valuing organizational stability over just a paycheck. An improved focus on mental health, conflict resolution and work/life balance will also be a big part of attracting the appropriate talent to an organization.

Source

https://redd.it/11nlocg
@r_devops

OpsLevel and Backstage ? What those are used for anyone has experience with those ?

Title

https://redd.it/11njlgy
@r_devops

Running Jenkins as Docker, but cannot execute docker commands from inside

Hi,

I've deployed Jenkins as Docker container in my local. But, when I try to execute job with docker command, it simply doesn't work.

+ docker ps
Failed to initialize: unable to resolve docker endpoint: open /certs/client/ca.pem: no such file or directory

What I am trying to do?

I have installed Docker in my host machine and want it to be accessible inside a docker container that is running Jenkins. I really don't get the .sock thing.

​

Installation Followed: https://www.jenkins.io/doc/book/installing/docker/Built Jenkins docker image using Dockerfile (as it comes with blue ocean).

Thanks.

https://redd.it/11oeej1
@r_devops

I’m writing a review article about popular WAFs for open-appsec. If you use any of the WAF solutions mentioned below, I'd love to feature your expert take on a few questions and link to your book, website, LinkedIn profile, YT channel.

WAF solutions: Cloudflare, Imperva, Barracuda Networks, Amazon Web Services, Akamai Kona, Fortiweb, Azure WAF, Prophaze, F5 AWAF, NGINX app protect, AppTrana, Sucuri, WAF Citrix WAF, NAXSI WAF, ModSecurity, Ironbee WAF, Octopus WAF, NGINX WAF (open-source), Coraza, Shadow Daemon, Web Knight, Vulture WAF, Haltdos WAF CE.

Questions:

What single feature made the waf solution you use to stand out?
What are the pros of the waf solution you use (please list at least three)
What single feature makes you most uncomfortable about the waf solution you use
Please list three cons of the waf solution you use.
Please share a screenshot of the dashboard of the WAF solution you use (please blur all sensitive information).
Feel free to recommend any good WAF solution that isn't on this list. Thank you.

​

PS: The aim of this is to get unbiased opinions about these WAF solutions. I'll be very grateful if you help me out. I'll be in the comment section.

https://redd.it/11ku18l
@r_devops

SigNoz the open-source DataDog alternative

Hey,

I've written a small article on SigNoz, an open-source monitoring tool for logs, metrics and traces all in one place. While it's not (yet) as mature as DataDog the developers are really active and are building not just a great product but also a great community.


https://www.infrastructureposts.com/p/signoz-the-open-source-datadog-alternative

https://redd.it/11oh5j7
@r_devops

In Github Actions, when you download an Artifact, do you need to reference it's path to use it in a Deployment?

I've got a solution I'm trying to fix (translating an Azure DevOps pipeline over to Github Actions which is a bit more a nightmare) but I want to download an artifact and use it's contents to deploy to Azure.

In the final "Deploy to staging" step, am I setting the package path incorrectly, should I reference the downloaded artifact? The documentation is pretty bad on this so any help would be welcomed.

I'm not able to download the actual artifact (it says it's downloaded so no files appear). Thanks.

- name: Compress Solution File
run: |
$sourcePath = "${{ env.RUNNER_TEMP }}\WebAppContent"
$destinationPath = "${{ env.RUNNER_TEMP }}\WebAppContent.zip"
Add-Type -AssemblyName System.IO.Compression.FileSystem
[System.IO.Compression.ZipFile]::CreateFromDirectory($sourcePath, $destinationPath)

- name: Upload artifact
uses: actions/upload-artifact@v2
with:
name: drop
path: '${{ env.RUNNER_TEMP }}\WebAppContent.zip'

- name: Download artifact
uses: actions/download-artifact@v3
with:
name: drop
path: '${{ env.RUNNER_TEMP }}'

- name: Log in with Azure
uses: azure/login@v1
with:
creds: '${{ secrets.AZURE_CREDENTIALS }}'

- name: Deploy to uat-staging # deploys to uat-staging
id: deploy-to-uat-staging
uses: azure/webapps-deploy@v2
with:
app-name: Webapp
slot-name: staging
package: "."
publish-profile: ${{ secrets.AZURE_WEBAPP_STAGING_PUBLISH_PROFILE }}

​

https://redd.it/11oiv98
@r_devops

Is Roadmap.sh's Devops Roadmap good for beginners?

So, I have finally decided to be a devops after researching a lot of thing as to what I should choose in software development career, so, I want to ask if Roadmap.sh website's Roadmap for devops a good thing to follow? If not please provide some tips of point me in right direction.

Here's the Roadmap I am referring Devops Roadmap

https://redd.it/11oj8ka
@r_devops

What job am I doing?

I work labelled as a software engineer 1


Things I do/ have done:

1. patch servers
2. develop apis(spring boot)
3. aws solutions (can configure bunch of stuff manually, terraform in noob phase)
4. testing framework
5. CI/CD e2e flow
6. ansible automation
7. slowly create awareness on unit test case and automating testing importance
8. now taking up nifi automation and stream lining it

​

This all made me feel like a any key guy, I don't have specialization in any one. They don't even task me with development work, I have to check with all PM to see if any dev work is available, if no dev work I just work on process improvement POC, BAU and KLO work


Is this a good practice? DevOps is a broad term and includes lot of stuff but is it ok to not specialize in one thing. will this approach of work make me a liability when searching new jobs


I may start applying for new job and just wanted opinion on understanding type of work I'm doing and tailoring my resume and job application

https://redd.it/11oh4el
@r_devops

What would you focus on?

Hi all - I work in the sales/customer success area of DevOps. I’m not an engineer and don’t claim to be, but I do love the DevOps space because I find it endlessly interesting.

As someone who will never be as technical as most all of you here, if you were me what would you spend your time studying to add more value to folks like you?

https://redd.it/11omqyx
@r_devops

How to SSH into Private VM in GCP

This is one of my favourite use of IAP to connect to VMs or GKE without exposing anything to the public internet.

https://youtu.be/FUL-ZM5yMrQ

https://redd.it/11oppv7
@r_devops

Starting on-call rotations in a company that doesn’t have them

I work for a large multinational brand retailer that is increasingly developing its own applications to keep up in the digital customer experience arms race.

One thing we have never had up until now is a proper incident management process or on-call rotations. The cost of a production-down incident here can exceed six figures per hour, so…we should probably get on that.

I am well familiar with the You Build It, You Run It model and all of the tooling that goes with it. What I’m more curious about is the human side of this - how to introduce on-call in a company that doesn’t yet have it, and how to navigate and negotiate the HR and compensation implications of that.

Please send me your war stories.

https://redd.it/11oqf0g
@r_devops

How long does it typically take you to get a job when your in the market?

Do you think current layoffs and what’s going on in the economy is making it harder to get hired or no change?

https://redd.it/11orxyl
@r_devops

Helm: Is it possible to merge base values.yaml's with stage specific values.yaml's

Apologies for the title, but I can't come up with a better one right now.

I am sitting here for hours thinking about how to restructure our repository in the best way to avoid redundancy and manual tasks as much as possible. Please note that I am pretty new to the whole kustomize world. Also, as a side note, we are using argo-cd.

That said, I was hoping it would be possible for us to use a structure like this:

./
├── base/
│ ├── app/
│ │ ├── Chart.yaml
│ │ ├── templates/
│ │ │ ├── deployment.yaml
│ │ │ ├── service.yaml
│ │ │ └── ...
│ │ └── ...
│ ├── db/
│ │ ├── Chart.yaml
│ │ ├── templates/
│ │ │ ├── deployment.yaml
│ │ │ ├── service.yaml
│ │ │ └── ...
│ │ └── ...
│ ├── app-values.yaml
│ ├── db-values.yaml
│ └── kustomization.yaml
├── overlays/
│ ├── dev/
│ │ ├── app/
│ │ │ ├── values.yaml
│ │ │ └── ...
│ │ ├── db/
│ │ │ ├── values.yaml
│ │ │ └── ...
│ │ └── kustomization.yaml
│ ├── staging/
│ │ ├── app/
│ │ │ ├── values.yaml
│ │ │ └── ...
│ │ ├── db/
│ │ │ ├── values.yaml
│ │ │ └── ...
│ │ └── kustomization.yaml
│ └── prod/
│ ├── app/
│ │ ├── values.yaml
│ │ └── ...
│ ├── db/
│ │ ├── values.yaml
│ │ └── ...
│ └── kustomization.yaml
└── ...


My plan with this is to have base values.yaml's that contain all the values that are identical for every stage, and then to merge these base values.yaml's with the ones containing the values that are unique to each stage. I was hoping I could use of inheritance and just pass multiple values.yaml's to our kustomization.yaml's, but I couldn't figure out a way that works. After hours of trial and error, my brain is tired now, and I was hoping somebody could lead me back on the right track.

Also, please consider: We do not have Internet access from our customers GKE clusters. We are pushing our own GitLab repository to the GCP and everything else happens inside their clusters. Compliance reasons...

https://redd.it/11otrnc
@r_devops

what is your ideal branching strategy?

In context, I’ve probably experienced many kinds of branching strategy:

1. The so-called ‘each environment one branch’ strategy where u might have your environment, test, dev, staging and yada yada which follows a unique branch.. this seems to be the most popular one (from where I am). It’s all fine and dandy until the team decides to patch something in the prod branch and ‘forgot’ rebase to other branches. Not a good experience in general.
2. Similarly, there’s also this ‘each version one branch’ strategy. I mean… why would anyone do that?
3. The ‘git flow’ strategy or any other variations of it where you have a so called masterpiece branch with other sub main branches like it could be dev, rc-xyz, unstable-01 and yada yada.. then you have your devs working off any of these sub branches, whether is for a feature or something.. then someone came along and decided to patch something in your masterpiece branch and another person merges one of the sub branch into another sub branch and now a team lead decided that his rc-xyz is ready and tested and shall now be merged as part of the masterpiece branch.. suddenly you have yourself a spaghetti mess of conflicts. man, I absolutely hate this strategy. I have lost count the number of times disasters happens due to this. Having to merge/fix/cherry-pick/whatever one branch to another while resolving conflicts along the way probably took a good chunk out of my lifespan.

And then comes my ideal branching strategy overall - the one and only single branch, literally strategy. Why? Because:

- everyone work off the one and only branch, main.
- it makes PR a lot more simpler and easy, we only have to review once!
- encourages making explicit and good commit (no more having 1 commit that has a bunch of other nonsense)
- encourages responsible code change (you think twice before making breaking changes)
- regressions are handled almost immediately (things breaks and affects everyone, it is handled almost immediately before it goes to our QA)
- cleaner single line of history

When I implemented this workflow and strategy to my team, it does takes a while to get used to it but I now live happier managing 1 stupidly large monorepo (it’s 2 monorepos in a monorepo that I somehow inherited), 4 frontend, 2 ios and 2 android projects with teams across continents.

But I do want to hear your thoughts and see how I could improve it further, what’s your ideal branching strategy?

https://redd.it/11oroqf
@r_devops

Seeking Help With a Career Change

I am currently a GIS Coordinator for a small utility and do consultation on the side for a variety of organizations across the US. For a better career outlook, I am wanting to formalize other skill sets so that I can market myself to different positions.

I currently am most comfortable with Python, and have a large amount of exposure to JSON and HTML. I am comfortable with a lot of networking principles and system administration, and regularly tinker with a small home lab machine and virtualization (Ubuntu).

What I am trying to figure out, is how do I get started in formalizing these skills without going back to a formal institution? I have looked into resources like Coursea, but I am not sure how valid these solutions are and/or if they are worth the costs. Does anyone have suggestions?

​

Thanks

https://redd.it/11oqg1f
@r_devops

SVB Exposure

Does anyone know which startups have exposure to Silicon Valley Bank?

https://redd.it/11oy9ue
@r_devops

Github Actions in monorepos

Not sure if this can be useful to someone, but I just released `hawk`, a little tool to help you manage `github workflows` in monorepo.

Docs can be improved but it does the job 🙃

​

https://github.com/Rawnly/hawk

https://redd.it/11p1fp4
@r_devops