nibblebit

joined 1 year ago
MODERATOR OF
[–] nibblebit@programming.dev 3 points 1 year ago

It depends... The myriad of reasons to have a dedicated release day have often to do with synchronizing marketing, support and the other departments.

My question is what does QA mean for your org? Does it mean defect detection? Testing? Acceptance? Those are all different things. The teams i see that are able to release every day have a strict separation of Quality Control and Functional Acceptance. QC used to detect defects and regression and is handled by highly automated processes accounted for by engineering. Then acceptance is done by a dedicated product/quality team that figure out if the new functionality actually is built to spec and solves the customer problems. This also involves blogs, documentation, customer contact, release notes, tutorials and workshop for the support team etc... This second part is handled by feature flagging, so that the product teams can bèta test, run a limited release and track adoption.

It really depends on what kind of software youre running and what your relationship is towards the end user and the rest of the org. Something that is the same in all cases is that your requirements and acceptance criteria need to be very clear from the start and regression resting needs to be fully automated.

[–] nibblebit@programming.dev 3 points 1 year ago
  1. You need as many environmental reminders that you are doing work as possible:
  • dedicated work place where you don't game or browse or do chores and taxes on.
  • dedicated work time where you are allowed to do work.
  • dedicated non-work time where you won't work and don't get to feel bad about not working on the project and avoiding negative emotions associated with the work.
  • I have a dedicated work shirt only worn while at work
  • figure out your attention sinks: music/podcasts/YouTube w/e and apply them strategically to signal that you are or are not working
  1. Plan. Identify as many tasks as possible ahead of time and figure out what is motivational an demotivational. Motivation takes a nosedive once the low hanging fruit runs out.
  • make sure to front-load the boring stuff and keep motivated by anticipating the fun stuff later. Please, Start out with the tests. TDD is a hack for ADD
  • Ration your creative sessions. Once you feel you are plateauing force yourself create some novelty in the project.
  1. Want and grit. At some point you'll have to grit it out. You have to make it clear to your brain that you want it. Make it personal. Want it not the way you want to have a cookie after dinner, want it the way you want to breathe. Don't even want the project, but want to prove to your brain that you are a rare capable human, able to start and finish a creative endeavour independently.

  2. Make work time scarce and urgent. Having a child has done wonders for my creative output. I used to splurge 6 hour sessions kinda working on something..now I get maybe 40 minutes a day. An hour if I'm creative about it. But heck, does that hour get applied like nobody's business.

Hope this helps, best of luck!

 

Hi! I'm a software guy and would like to start out doing some robotics. Before I go out and get a bunch of hardware. I'd like to practice the fundamentals.

I'm most comfortable with C++ and C# and dotnet and am pretty comfortable with game engines like Unity Unreal and Godot.

I've started out modeling a three-joint articulated robot arm that i can control through signals to the individual joints, like controlling a stepper motor.

My goal is to figure out a system where I can declare the shape of a robot like this (armature size, number of joints, offsets etc) to create a virtual model of the robot. I want to be able to send target coordinates and a basis rotation to that model and receive a series of signals back that will move the head of the robot to that 3d coordinate and rotation.

Now, I'm sure there are systems and packages that do all the math for this already, so what tools/libraries do you guys use to do modeling like this?

I want to see if I can simulate it in a game engine, and if that works out maybe ill try it on a toy :D

Thanks!

[–] nibblebit@programming.dev 1 points 1 year ago (1 children)

Theres like a whole class of "Stuff you have to relearn every time you have to use it": XPath, JMESPath, cron, ffmpeg, ImageMagick, PostScript etc.. REGEX might be king of those :p

[–] nibblebit@programming.dev 0 points 1 year ago (3 children)

Also works for cron jobs, shell scripts, SQL queries, HTML layouts and the odd mermaid diagram

[–] nibblebit@programming.dev 0 points 1 year ago

A single race condition is a tragedy. A million race conditions is eventual consistency.

[–] nibblebit@programming.dev 1 points 1 year ago

What I love most about Krazam is that in every video they make, you see the guy move up the usual tech career ladder xD

1
Lemmy on native Azure? (raw.githubusercontent.com)
submitted 1 year ago* (last edited 1 year ago) by nibblebit@programming.dev to c/loud@programming.dev
 

Hey! Last week I tried off and on to get Lemmy running on an Azure subscription, it's been tricky.

I still haven't gotten it working correctly. So far, I've tried to run the docker-compose on an ACI and Container app, but I've had the most success on a Web App for Containers of all things with the configs uploaded directly on the app service through FTP (yeah...).

I'm running the Postgres as a separate Flexible server instance (set it to v15, default is v13). And I'm running the pict-rs container as a separate ACI with a mounted storage account.

Right now the backend doesn't want to run db migrations fully, but I'm not sure why, otherwise the rest seems to work as intended and can scale independently. Running up to a projected $52/month with everything on the lowest possible SKU

I will publish a bicep once I get the whole thing to run reproducibly.

Have you guys tried it out? What other approaches have you tried or would you try?

[–] nibblebit@programming.dev 1 points 1 year ago (2 children)

I've been trying to setup a working instance using container apps, web apps for containers and ACI, but it remains finicky. Do you know of a bicep or deployment script that does this properly?

[–] nibblebit@programming.dev 0 points 1 year ago (1 children)

It's difficult problem to solve. Lemmy's stack is a bit unconventional. The rust backend is not idiomatic and the ui is based off a template of an isomorphic not-quite-react framework. Its not impossible, but it will take a while for alot of programmers come onboard.

That being said, there's more to it than writing code. Better bug reports, reproduction, updating docs and triaging/managing the issues is possibly more important than writing PRs. Don't be discouraged!

 
 

Hey there! 👋

Welcome to our C# community on Lemmy! We're a group of programmers, hobbyists, and learners all keen about C#. Whether you're a pro or just getting started, we're excited to have you here.

Our goal? To learn, share, and collaborate on everything C#. Got questions, projects, or resources to share? Or simply want to discuss a feature you love (or not) about C#? This is your space!

Here are a few ground rules:

  1. Be respectful and considerate: Remember, we're all at different stages in our C# journey.

  2. Stay on topic: Let's keep discussions C# focused.

  3. No spamming or self-promotion: Share your projects, but don't overdo the self-promotion.

  4. Use appropriate language: No offensive language. Let's keep it positive!

So, let's dotnet build and Nuget Unable to resolve dependency

Cheers!

 

Hey Guys. I thought it would be fun to setup a public anonymous survey about our users. Just to see what kind of different cloud adopters we have around. Results are public and entry is anonymous. It's only to be used for the community.

For now it's as simple as taking a look at what you guys are using and what you are curious about, but in the future we can expand it to answer some interesting questions :)

 

Hey everyone,

I thought it would be good to set up a repository of learning materials beneficial for both newcomers and seasoned professionals.

The aim is to curate content that ranges from beginner to advanced levels, either focused on specific cloud platforms like AWS, Google Cloud, Azure, IBM Cloud, etc., or general insights applicable across multiple platforms.

The three main categories for suggestions are:

  1. Books: What are some introductory and advanced-level books that have deepened your understanding of cloud computing? This could include architecture, best practices, security, scalability, serverless computing, cookbooks and others.

  2. Blogs: We'd love to know which blogs you trust and follow for the latest news, trends, and innovations in cloud computing. Technical blogs offering how-to guides, problem-solving techniques, project logs and tutorials, or sharing personal experiences in the field would also be great.

  3. Videos: Are there YouTube channels, online course platforms, or websites that have provided you with insightful video tutorials, webinars, or talks on cloud technology?

Cloud computing is a big field, so here are some suggestions for interesting topics:

  • IaaS, PaaS and SaaS offerings of different providers
  • comparisons and cross-platform mappings (eg. Azure for AWS engineers)
  • IAC solutions
  • Authentication, Security and Access control
  • Architecture
  • Big(ish) Data management
  • Governance, compliance and Monitoring
  • Fun personal projects

Thank you so much!

 

Hello and welcome to /c/loud, the community for everything cloud computing. We are a growing community of IT pros, developers, tech enthusiasts, and novices alike, all with a common interest - exploring and understanding the expansive world of cloud technology.

This community was created to foster meaningful discussions, insights, and knowledge sharing about cloud computing. Here, we delve into everything from the fundamentals of cloud architecture to advanced topics, such as implementing cloud-native applications and mastering different cloud services like AWS, Google Cloud, Azure, and many others.

What Can You Expect From /c/loud?

  1. Discussions: There's always a vibrant conversation happening here. You can ask questions, answer queries, engage in debates, or share your insights about various aspects of cloud computing.

  2. News: Stay up-to-date with the latest developments in the cloud computing world. From new service launches to policy changes, we discuss it all.

  3. Learning Resources: Whether you're just starting with cloud computing or are a seasoned professional looking to expand your skills, we regularly share resources to helThere's something for everyone, fromu. From online courses, tutorials, and webinars, to blog articles ething for everyone.

  4. Career Guidance: Interested in a cloud computing career but unsure where to start? This community can be an excellent resource. Share your career-related questions, get advice from industry veterans, and learn about job opportunities.

Rules

Remember, as with all communities, we have a few rules to ensure the conversations remain respectful and relevant. Before you post, please take a moment to go through our rules.

  1. Respect Each Other: Everyone has a right to their opinion. Please respect that right. Healthy debates are fine but do not resort to personal attacks or hate speech. We value a diverse community with different perspectives.

  2. Stay on Topic: This is a cloud computing community, all discussions and posts should be related to this subject. Please ensure that your posts are relevant.

  3. No Spam or Self-Promotion: This community is a place for discussion, not self-promotion or advertising. Posts that blatantly advertise a product, or service, or are used for self-promotion will be removed.

  4. Avoid Reposting: Before posting, please use the search bar to ensure the topic hasn't been covered recently. Repetitive posts can clutter the feed and might be removed.

  5. Professional Language: Use professional and (hekkin') polite language. Avoid using inappropriate or offensive content. Firefly profanity is allowed.

  6. Fact-Check Your Posts: Misinformation can be damaging and misleading. Please ensure that the information you are sharing is accurate to the best of your knowledge. This includes outdated articles or content regarding deprecated services.

  7. Respect Privacy: Do not share the personal information of others. This includes email addresses, phone numbers, physical addresses, etc.

  8. No Illegal Content: Any posts or comments sharing illegal content, or discussing activities that violate the terms of service of cloud computing platforms, will be removed.

  9. Cite Your Sources: If your post includes data or information sourced from somewhere else, please provide a link or citation to the original source.

Violation of any of these rules can result in post/comment removal. The mod team reserves the right to enforce these rules at their discretion. If you have any questions or concerns, please feel free to reach out to the moderators.

We look forward to a positive and engaging environment here in our community!

Enjoy!

Whether you're exploring cloud computing for the first time, or you're an experienced professional keen on staying abreast of the latest trends, /c/loud is the perfect place for you. Join us today and become a part of our thriving community!

[–] nibblebit@programming.dev 1 points 1 year ago

Article is a bit dated and hard to read. The gist of the author is relatable though 15 years later: redundancies have been hella annoying, especially if they are unknown. Bad abstractions, however, create dilemmas, dead-locks and chicken-and-egg situations. And it's impossible to create good abstractions unless you have no colleagues and no customers.

I would take some frustration over grinding to a halt any time.

view more: next ›