-
Estimating complexity vs time ….
Estimating complexity vs time… it cannot be done one without the other. First i will write why we should estimate complexity and then a very short point ’cause in the end…’. At least this might feel like it for some of us… Why should we estimate complexity in scrum Overall, estimating complexity versus time in Scrum promotes a deeper understanding of project requirements, enhances collaboration and communication within the team, and enables more accurate planning and risk management, ultimately contributing to the success of the project. Why estimating anything doesn`t really work I totally agree that splitting the task in smaller steps is the best thing we can do. Smaller,…
-
Effective Programming in Scala course by Coursera. Simple review.
Effective Programming in Scala course by Coursera is one of the official learning paths, described on https://www.scala-lang.org/, one can take to learn and dive into scala language. The main outcome is that You should definetly try it but there is always some „but”. Main things to do Lectures During the course You will watch short and very neat and straight down to the point lectures. This is always a given in every course. If i remember my long hours and the university i wonder how did i endure all that and why everything was so convoluted. Here we get everything short and sweet. Coursera time frame Somethimes it might feel…
-
GitLab dev to qa merge conflict with no resolution options
GitLab dev to qa merge conflict with no resolution options can occur on multiple different occasions. One of the main reasons You can run into is : You can still check it out locally. The merge request You will be able to see and resolve in intellij or command line, whatever You fancy. At least you will be able to pull and just use the things that causes the conflic from QA. Unfortunetly it might require You to work on some changes again. For more stability i would do it one branch after the other so gitlab will not have issues when we first merge everything from QA using qa…
-
Before:2023 google hack – get results before the AI crap
Before:2023 – add this before the search query and get results before the AI crappy era. In addition it should also render a lot more organic results without pesky ads. Since the algorith changes it feels like everything thing is either sponsored or just plain in ad. Call me a tin foil hat but the dead internet theory isn`t that dead anymore 😉 I miss the internet where people blogged and wrote their thoughts like on myspace. Too bad it didn`t work out, everything got monetized. Try to add „+blog” to hopefully find a personal blog of a person that really dug into your problem and has a nicely documented…
Zobacz również
Commonly used sentence in AI NLP speech recognition ?
-
Vite findByText to get all the elements
Vite findByText method could help us a lot, especially while testing any kind of i18n and similar. Of course we should always get the proepr component / element but such methods are very usefull when developing and debugging, later we can scrape it all. Later, when we know it works as we expect it. FindByText method can be especially usefull when we have a big flat table that may or may not be dynamically populated. Works great as a function to watch the vaues beeing present in the dom so we can catch the proper moment. Altough we could use the debugger, i find that printing a lot of stuff…
-
How to wait for a reactive vue component like tooltip ?
How to wait for a reactive vue component like tooltip ? That`s a tricky one, especially while everything is rendered dynamically and we really need to know where to look… or how to wait… Testing asynchronouse components Vite waitFor Wait for the callback to execute successfully. If the callback throws an error or returns a rejected promise it will continue to wait until it succeeds or times out. Vite waitUntil This is similar to vi.waitFor, but if the callback throws any errors, execution is immediately interrupted and an error message is received. If the callback returns falsy value, the next check will continue until truthy value is returned. This is useful…
-
!! operator in vue components
!! operator (double negation) transforms values into boolean values. This ’!!’ operator converts any value to TRUE if it’s „truthy„, meaning it’s not a falsy value (such as false, 0, empty value, null, undefined, NaN), otherwise it converts to FALSE. !! operator examples : For example, if you have a variable myVar, and you want to check if it’s „truthy” or „falsy”, you can do it using the !! operator like this: Another example is when the !! operator helps to validate any optional variables. Somethimes we really have no idea what we will get, this can vent some issues if we need to check for a truthy or falsy…
-
Locality of Behaviour
Locality of Behaviour is a great principle that should help with maintaining the code. This is the characteristic of the code that enables a developer to only read a small portion of code to understand its function. Without the need to skip, skim, read, jump all over multiple files. I love that rule cause it DOES MAKE SENSE. I can see many places where we would benefit from it but not always do it that way because of the 'standard’. Which, in the end, nobody knows what it is anymore cause everyone is mixing patterns, antipatterns and the number one performance metric is how fast you can deliver… maybe i…
-
Scala pipe operator „|>”
Scala pipe operator „|>” passes the result of the left side to the right side method/function as the first argument. t is, one might argue, „yet another arrow”, that provides „something” to be put „somewhere”. This is absolutely true but in addition it provides readability. Scala pipe operator „|>” source code It is just a simple fancy looking generic function : IThis operator shines if Your code at least tries to follow rules written down by Uncle Bobo and his clean code mentality. This allows you to chain function calls in a more natural left-to-right order, which can sometimes be more readable than nested function calls. Just don`t get overboard…
-
Commonly used sentence in AI NLP speech recognition ?
The commonly used sentence in AI NLP speech recognition is The quick brown fox jumps over the lazy dog AI for everyone The curiousity about that particular sentence is that it containes every letter in the alphabet, from A to Z. It is also called a pangram or a holoalphabetic sentence. Uses every letter of a given alphabet at least once. Pangrams serve various purposes as showcasing typefaces, testing equipment, and honing skills in handwriting, calligraphy, and typing.
Zobacz również
Before:2023 google hack – get results before the AI crap
