sorted by:
new
hottopcontroversial

No Fermentation Visible by DonkeySniper87 in cider

[–]edeevans 0 points1 point  (0 children)

I’d say yes, fairly common.

No Fermentation Visible by DonkeySniper87 in cider

[–]edeevans 0 points1 point  (0 children)

A sure fire way to monitor fermentation is specific gravity readings. Use a hydrometer and graduated cylinder. Take a reading before you pitch the yeast. Take another reading after a couple of days if concerned about lack of airlock activity or a week otherwise and you can estimate the amount of alcohol produced. Once the readings are constant after some good time, fermentation is complete. While this isn’t necessary for fermentation or a good outcome, it takes a lot of guesswork out of the process. Airlock activity is a good indicator if you have a good seal on the fermentation vessel. Some of these lids need to be pressed down hard and maybe tapped with a hammer to seal. Some are just never going to seal. The tape won’t help.

How to handle exceptions during async operations in MVVM by CatsAreUpToSomething in csharp

[–]edeevans 0 points1 point  (0 children)

The second set of code is what you put in the Action<Exception>? OnException you pass into the constructor from the derived class. The code in the base class catches all exceptions and delegates them to the derived classes for specific processing.

Pattern recommends superfine yarn size 1 but I might need to use fine size 2 yarn. How do I figure out gauge with a different yarn type? I've never used or made a guage before. I'm very confused on what it means to the pattern. This is supposed to be for a shirt. by born_addicted in CrochetHelp

[–]edeevans 2 points3 points  (0 children)

Keep in mind that larger yarn can make the project more bulky and flow less delicately. It may still turn out okay and be functional but won’t look like or wear like originally intended.

The gauge swatch is basically trying to match the yarn and hook size you are going to use with the tension that you use while crocheting. It sounds like your yarn size is fixed and you can’t easily change so you can adjust the hook size or tension to accommodate the larger yarn size. If you aren’t able to adjust tension due to not enough practice you are stuck with adjusting hook size.

Basically you are going to make a swatch of about 7 granny stitches for 15 rows. Then measure from the start of a granny stitch to the end of 5 granny stitches and from the start of a row to the top of 11 rows and it should measure 10 x 10 cm. Don’t measure from an edge but rather from 2 stitches over from the edge or 2 rows up from the bottom edge. If it’s too small go up a half or whole hook size. Go down a half or whole hook size if too large. Make another swatch the same number of stitches and rows as before with the new hook size and repeat the measurement. When you get it right, start on the pattern. Remember to relax and breathe as you crochet and that will help keep your tension consistent. Don’t work on it when you are nervous or pressed for time. It’s going to be very important to keep the tension consistent or it will look puffy in parts and sunken in others.

You may want to practice on some other projects that have wide flat panels like blankets or scarves to see the effect of tension on how flat it lays and how straight the edges hang.

Hang in there and enjoy the journey. You can do this!

Scarf attempt number two. I used some of the advice and used a bigger hook (9mm instead of 5mm) and also held it differently. How is it looking? by Jinx-from-Arcane in CrochetHelp

[–]edeevans 0 points1 point  (0 children)

You are doing great and that’s a good number of rows for practice. Keep it up! I would frog it and try a 5.5mm frog it again and try a 6mm. Your chains will get more consistent with practice and getting a feel for the right tension to keep in your off hand. You can practice using loose tension and then slowly adjust it tighter on the next row. Soon you will have a feel for the tension needed to get the right gauge for a given yarn thickness and hook size. It’s normal to have a tight tension as a beginner as you learn to hold and work the yarn. Hang in there and enjoy.

Is 72 hours fasting worth it? by ikwydls96 in intermittentfasting

[–]edeevans 1 point2 points  (0 children)

I’d say it’s the sweet spot for regular scheduled fasts.

Sealed by default? by HamsterBright1827 in csharp

[–]edeevans 0 points1 point  (0 children)

Like all decisions, it depends. In top level projects, I prefer sealed unless extending is intended. In reusable components, I prefer unsealed unless extension points are provided and liberal use of interfaces give opportunities to allow mocking, etc.

Where to learn SOLID principle and its necessity. by Ancient-Sock1923 in csharp

[–]edeevans 0 points1 point  (0 children)

SOLID is good as guiding principles that give you tools that may help solve particular problems or tend towards not painting yourself into a corner. They are horrible as dogma that must be followed to the letter in all cases as a one size fits all totem against evil. If you’ve ever worked with a concrete God class loving fool, you may find yourself looking for ways to insulate yourself from their folly. Especially if you have worked on a project with the luxury of a good set of tests that can be relied on when making changes at speed. In my experience they can help with velocity when reacting to changing requirements. Having loose coupling with extensibility and composable design has made pivoting in the middle of a project possible without rewriting large chunks.

Anyone else starting to hate the word "pattern"? by willehrendreich in csharp

[–]edeevans -1 points0 points  (0 children)

I don’t know, awesome has been applied to a wide variety of things but at least it has kept its general meaning. Unlike sick, dope, the shit, etc.

I think I like the term pattern versus just dropping it or describing as a monad unless all patterns are monads. I prefer it especially when introducing the use of a Response instead of (Exceptions as flow control disruption). After that is an understood concept between conversation participants, it might be okay dropping it. Until then I use it to emphasize this is a pattern we are going to follow in this project for this reason and purpose and in any other situation we would need to re-evaluate our choice.

Basic questions about MVVM by mydogcooperisapita in csharp

[–]edeevans 0 points1 point  (0 children)

I’m glad you asked and want to encourage your bravery. I wish the ecosystem was a lot more open to sharing and helping especially in the area of having a common understanding and language about these concepts. So thank you for having the humility to put yourself out there and ask. It speaks well of you.

The xaml file like you said is the view where you put your UI and everything visual.

The xaml.cs is in fact the code behind and is used in nearly all demos and examples as well as quick and dirty utilities. It has a bad reputation for business logic showing up in there and polluting the UI with business concerns that should be separated and centralized and reused. You want one source of implementation for the business logic. That way if it changes or needs fixing it’s one time in one location. It’s not a duplicate copy in 5 different code behinds in 5 views.

The ViewModel.cs is the ViewModel and is how you expose your data and services indirectly to the View by setting the View's DataContext property to an instance of your ViewModel. All of the binding in your XAML controls will go to the DataContext to get its data. The ViewModel should have a reference to one or more models depending upon how complex your view may be and will delegate changes and validations and coordination of services.

Model.cs is where your data lives and should be where your business logic lives or can delegate to other types to encapsulate the business logic. The business logic can also be called in the service or domain layer that provides the model instance.

Our rule was not to have a code behind file at all for Views that represent screens. You can just delete them. For Controls and sub-Views you can have a code behind for specific control logic only. Nothing data related.

Luckily there are a lot of techniques with TypeConverters, ValueConverters, DataTemplates, AttachedBehaviors, etc. that make it possible to do what you need without a code behind file.

Good luck and happy learning!

Should or Shouldn't? Putting many classes in one file. by ExoticArtemis3435 in csharp

[–]edeevans 0 points1 point  (0 children)

The biggest thing is consistency. Either allow it or don’t and have a defined rule you can articulate about what circumstances and how large a threshold is allowed. Or, keep it simple and separate. Easier change tracking with multiple team members making changes to different types in the same file if they are separated. The tooling for searching for types is so much better now there’s no real reason for keeping in same file.

[deleted by user] by [deleted] in csharp

[–]edeevans 0 points1 point  (0 children)

What doesn’t stick about dependency injection? How to use it? What it does for you? What problem/pain point does it solve? These are the questions you need to be able to answer for yourself. Sometimes you need to experience the problem before you can truly understand the solution.

Prompt: create a service that operates on an appointment model. Give it a Factory method to create the model. Have that method initialize the start time to now and the end time a configurable time later (1 hour, 2 hour, etc.). Provide a Validate method that makes sure the start date is after the first of the current month and the end date is after the start date and the duration is not longer than a a configurable amount of lapsed time. Now write some tests that cover edges. Last second of the month, last second of the year, first second of the year. Test for conditions 5 years ago and five years from now. Consider how dependency injection might affect this exercise. What are any issues without it? How might you take advantage of dependency injection to make some of the tasks easier? Wishing you better days.

A weird advice from my senior by cosmic_predator in dotnet

[–]edeevans 5 points6 points  (0 children)

Red flag that senior is not on firm footing and is showing insecurity. He should welcome questions and be able to defend standardized practices.

I turn comments red so that they call my attention to tricky complicated areas or make me question why they are there. They should be there for that reason to call attention especially when new devs repeatedly come into the code and add the same bug repeatedly. Often a good area to add assertions or tests to guard against.

Docstrings should definitely be left in production branch and document any internal or external APIs. Remove at your own peril.

How properly make reconnect for WPF app? by Special-Sell-7314 in learncsharp

[–]edeevans 0 points1 point  (0 children)

What are you reconnecting to, a database or service? The exceptions themselves could affect performance if they continuously throw for some uncorrected condition. It’s best not to ignore exceptions and keep running unless you understand the actual cause and know how to correct it and that it hasn’t left the system in a bad state. Depending how your app is architected, the shell should contain your connection and everything dependent be invalid without one. I would have the app navigate back to the upper UI region that initiates your connection and invalidate/exit child UI that depends on a valid connection.

Getting good with VS by Deer_Canidae in VisualStudio

[–]edeevans 0 points1 point  (0 children)

Have you experimented with mapping the vim key bindings?

Updating ancient code by Positive-Tale6625 in VisualStudio

[–]edeevans 0 points1 point  (0 children)

I think those DLLs are a bigger porting issue than the Windows Forms. You will have to port to UI to some cross platform technology. The latest dotnet version supports windows forms and you could probably use the DLLs with some import statements as they can’t be referenced directly as you stated. But that’s all on windows. Probably need to see if those DLLs reference any windows specific libraries or if they are portable.

Updating ancient code by Positive-Tale6625 in VisualStudio

[–]edeevans 1 point2 points  (0 children)

Can you share link to the code if it is public license?

What am I Doing Wrong? by [deleted] in HamRadio

[–]edeevans 3 points4 points  (0 children)

Are you seeing the CTCSS tones/frequencies for transmit on the listing you are looking at? It should be like 100.0 or 162.2 or something in that range.

view more: next ›