I am early in my programming journey and want to start building projects.
For example, I want to start playing around with some maths concepts, essentially coding a graph theory solvevisualizer and also maybe playing around with some other concepts.
The thing is, I only learned basic java in school, and the only UI library I am familiar with is JavaFX.
Sure, I could probably do what I want in JavaFX, but I wonder what is the value of this, since JavaFX is very rarely used in industry.
So I had the idea of making my graph theory visualizer on a website, as creating a website that could be used by students to help with their math problem would showcase that I am able to create a product that has real world utility.
So I set myself on this path of learning javascript, CSS, HTML and React and now that I am a third trough a React book, I ask myself the following question:
Am I putting too much energy on learning something that is not really close to my interests?
Throughout my studies, I found that I am mostly interested by maths and physics. I now find myself spending all my time learning a technology that is not close to any of the potential career paths that interest me (graphics programming, machine learning, physics simulations) just because I want to make my dumb maths project have a more practical aspect.
Am I wasting my time? Or is basic Web Dev a must for any kind of programmer?

I see a lot people that post in frustration and worry that they’ll never be “good” at programming, so I wanted to ask for some feel good moments you’ve experienced on your journey to learning programming… I recently had a pretty awesome moment that boosted my confidence, in my programming ability and knowledge.
TLDR: Hobbiest, worked on a personal game project over a year ago, came back to it to improve it, and found my code was well organized, well written, easily adaptable and expandable. Made me realize the studying I have done actually stuck, and maybe I’m not as green as I thought. :-)
I am a complete hobbyist, I work on projects solely for the joy of learning a new skill that just so happens be making video games, which I grew up loving, but have never understood how to program.
I started learning Unity and C# during the tail end of the pandemic, and I quickly discovered I really enjoyed coding, and making games, but understood that, realistically, at 37 years old, I would not be changing careers, so just took the process at my own pace, I worked through the C# Players Guide(5th edition, I think) I completed almost every tutorial series on GameDev.TV that had to do with Unity or C#, and watched many topic specific videos on YouTube, Udemy and skillshare…on topics like AI, Pathfinding, Procedural Generation, ShaderGraph, 2D, 3D 2.5d…
Rick Davidson, Penny de Byl, Brackeys, CodeMonkey, Jason Weimann, Tarodev… amoung many others, have been my teachers. I have made many small tutorial projects, and a couple larger “intermediate/advanced” tutorial projects, but nothing that was really my own, I’d just been enjoying the process of learning and making simple fun games.
Well, a little over a year ago, March 2023, I decided it was time to start my own project. I had no delusions of grandeur, I had no plans on actually releasing anything. I just had an idea for a game, and I wanted to see if I could build it from scratch. So I did.
My game plays like a 2 player board game, Two Factions: Good Vs. Evil, both factions with Three races to choose from (Humans, Dwarves, or Elves, and Demons, Monsters or Undead) with dice rolling, a hex grid game board, different phases for each players turn, combat between units( a basic attack that did a predetermined amount of damage), the goal was to collect 7 “energy” nodes randomly scattered on the board, 3 on each side of the board and one on the center Hex.
Each side takes turns moving their 3 unit types (a collector, a warrior, and an Overseer), around the board, trying to eliminate the other players collector, and collect the nodes before the other player. If a collector is destroyed you have to use collected energy to span a new one. Its all set in a fantasy setting, and the scene is set to look as if your playing a board game in a medieval pub.
I did some really complex (at least to me) things too. Each match is set on a procedurally generated game board, set to look like the chosen game board environment (ie, grasslands, sand dunes/desert, volcanic wastes, wintesnow).
I built my own state machine to manage each players turn. With multiple states, an optional “magical misfire” state, that only occurs if the player rolls a 1 during collection.
I built my own Camera Managment system utilizing cinemachine, it’s simple but it keeps track of which camera is active, controls the camera movement for each players camera… etc.
I built my own player notification system, that allows for timed notifications system that both sends to notification panel for immediate display, and also a log for players to refer back to if needed.
I have multiple managers to keep things compartmentalized, and as OOP as possible.
I created multi base classes that all have numerous heirs, and came up with ways to make everything customizable and unique. Each player has a choice of 3 factions, all with their own UI, their own HomePieces, each unit is unique, and it looks pretty good because I have been using humble bundle since I started learning to get a very large collection of synty model packs, and high quality UI assets.
After 3 months. I had a working game loop, a very customizable game board generation system, and had pretty much accomplished what I set out to do. Everything in my initial development document had been implemented. However, the gameplay itself wasn’t very fun. It all worked and looked pretty good, but it just didn’t have any umph. (I have not added any “juice” either, so it was pretty stale) I decided I had reached the point where I was a little lost on where to take it. I had been spending A LOT of time working on it, 4-5 hours a day on top of my full time job working customer service at the airport. Yes, I was enjoying it, but I burnt myself out, and I started getting frustrated that I seemed to be stuck. I could not think of anything useful or fun to add. I had ideas, but I couldn’t think of how to implement them… and if I did try something new, I couldn’t work out how to get it to sync up with every thing else, and things just kept breaking. I thought “I’m too deep at this point, and I must have too much spaghetti in my code.”
I felt happy with where this project had ended, as it was complete, and everything I had put in my initial planning document was implemented and working…and, I was actually really proud of some of the systems, like the hex grid generator, and the procedural terrain generation, and all the ideas I had about how to initialize the whole thing and get it all working over multiple scenes, with multiple players… I learned a lot, and really enjoyed it over all. I was happy, but felt I had taken as far as I could. Even though I had ideas I wanted to do, like different actions for each unit, different spells for each faction type, etc.
As I said, I was feeling burnt out, I had enjoyed the process but, it had taken its toll. So I took a break from Coding. Not really knowing how long it would be.
I got really into Oxygen Not Included, and spent hundreds of hours building colonies, and trying to reach the temporal tear… I have yet to make it, sadly. I then spent a while playing My Time at Sandrock, and happily built up my workshop, while helping uncover the conspiracy of the stolen water, and returned the desert to a lush oasis… I played many other games in between as well, finding myself analyzing the mechanics, the presentation, the feel… Then the itch came back. I hadn’t even opened Unity in almost a year. I had had a lot of ideas in the in between. Specifically ideas about what I could do to improve the game I had created. So, I thought”I’ll try something simple, see what I remember…“
I found, it was like hardly any time had passed at all. I was a little fuzzy on some things, and I needed a few reminders of syntax and other small things that popped up, but any issues or forgotten techniques were quickly remedied and remembered.
However, I was nervous to revisit my game. I remembered how frustrated I was when I decided to take a break. I just KNEW I had too many dependencies, I just KNEW everything was spaghettified mess and I would be in a nightmare of refactoring to clean things up. Plus, I had read so many Reddit posts about revisiting code, even from just a couple weeks ago, and the programmer not remembering anything about it… like they couldn’t even remember writing it, let alone what it did… So I thought it would be a futile experiment to try and improve my game.
But, I was curious if I could improve things, and add some of the ideas I’ve had. So, I opened up the project, and played my game for the first time in almost a year. I noticed a few issues right away, remnants of my final attempts to improve my game while at the end of a burnout, that I frustratingly couldn’t figure out how to fix at the time. Like the player pieces spawning in the wrong rotation (facing away the opposite of where they were supposed to face.) or the game board generation, if the board wasn’t viable, it was supposed to reset and start over to generate a new board… it was, but the finalization of the regenerated game board wasn’t receiving a certain list of prefabbed terrain tiles, and would spawn those as null, so nothing would appear, where there was supposed to be a terrain tile. So I decided tackle those two issues first.
I dove into the code… and to my surprise, where I expected to find a mess of random variable names, or confusing methods, that do multiple tasks, creating a grid of confusion… I found logical code that made sense. Properties were named in a way that I knew exactly what they were for and what they contained, I could follow the path way of calls and understood what was happening, where.. it had been almost year and I hadn’t even looked at this code, and I understood what was going on. I refactored/rewrote a few areas, and got the unit spawning rotation and the generation reset issues resolved. Surprised at how well I was understanding my old code. I decided to be a little bolder, and rework how moving the players units worked. Originally during the movement phase, the player would roll a D6 and could move each of its units, any number of spaces up to their dice roll, on the board. I wanted the different units to feel more unique, each with their own “stats” as it were, so I added a few variables, reworked a few lines of code, and soon enough I had the movement I was liking for, each unit with its own distance, no dice roll needed. Also, it was fairly easy. I was able to make the adjustments to the code and get the results I wanted without breaking things, without effecting any other aspect of the game, as intended, in a way that made total sense working with the other systems. I am now fairly certain that my frustration and inability to get the result I wanted or expected, was due to burning myself out, by not prioritizing my mental health over my enjoyment of coding.
I have since begun work on improving my game again, in earnest. With a healthier work/life/coding fun balance. I have been working for a couple more months since picking it back up. And I have been able to implement entirely new systems, such as a gamePieceAction system that allows each unit to have unique attacks and abilities, Allows for different types of ability use during the different phases of the turn, so collectors can have collection abilities, were warriors have combat abilities, and each players home can have support abilities like healing units, buffing units, etc…
I have added a FogOfWar system that disallows the players to see each others moves, and I have come up with a lot of ideas for how to improve things, and it’s all working and fitting together without causing a huge headache and without having to refactor half the code to work, my initial attempt was actually pretty good, and I am able to implement the ideas that I think will make it more fun, maybe I’ll get it to a point that I can share it for others to play too, and I am excited to be back to doing something I truly enjoy. Thanks for reading!

Wanting to move away from Dell Command, mainly because we are using per-device BIOS passwords now as part of the new BIOS Configuration device configuration profile so BIOS updates will fail anyway.
Windows Update offers a cool feature which allows you update the BIOS through UEFI firmware capsule which doesn't require the password. We already use WUFB w/ Autopatch - so it seemed like a no-brainer.
However, I can't for the life of me get any devices to pull down approved drivers from a ring I created a couple of weeks ago.
I have checked:

• Devices are compatible (W11 + AADJ)
• Drivers are 'allowed' in the Quality Update ring(s) (Checked registry values too)
• Drivers are 'approved'
• Telemetry is 'enabled'
• Windows Diagnostic data is 'enabled' at tenant level

When running through Graph API to get the applicable devices so I can troubleshoot further, I'm not getting 'matchedDevices' returned despite the GUI reporting that multiple devices are matched to the approved drivers.
WUFB is awesome, but driver rings just don't feel polished compared to quality/feature update rings.
Is it really this awkward/flaky or am I missing something obvious?
Looking to hear your experiences.
Thanks.

https://stackoverflow.com/questions/78474713/dax-power-bi-how-do-i-create-a-burndown-column-table
I have the expected number of items to close on each day in Date ECD, and another column for the actual amount closed on each day in Date ACD. So I have a table with one column having every day between 1/1/2023 and 12/31/2025. Below is a snippet of the table with data:
Date Date ECD Date ACD 5/11/24 1 1 5/12/24 0 0 5/13/24 2 1 5/14/24 1 2 5/15/24 1 0 5/16/24 0 1
The issue is creating two Burndown columns, that take a sum of ALL values in DATE ECD and DATE ACD, then reduces it by the value in the corresponding column each day. The burndown ECD can go on through to 12/31/2025, but once it hits 0, it should have #N/A as the rest of the values (this stops the graph from showing 0 after the burndown is complete). The Burndown ACD starts at the sum of Burndown ECD, and reduces every day there is a value in Date ACD, but should give a value of #N/A for every day AFTER today (or after it hits 0). Let's say today is 5/13/2024. The burndown table should look like this:
Date Date ECD Date ACD Burndown ECD Burndown ACD 5/11/24 0 0 6 6 5/12/24 2 1 4 5 5/13/24 2 2 2 3 5/14/24 1 1 #N/A 5/15/24 1 0 #N/A 5/16/24 0 #N/A #N/A
Thank you for your help!
I tried a few different measures, calculates, filters, sums, from other places online and Chat GPT and nothing has worked. Other solutions to similar problems did not produce the result I wanted.

I have more than 50+ repos with C/C++ files in it, most of the functions are inter-linked with each other (for running a particular function, it should know the context for another function in another file). I want to create a RAG system for asking questions related to functions inside them and improving or finding bugs and all.
Should I use vector stores with creating documents and chunks or should I use knowledge graphs or combination of both (which I don't know how to achieve, any internet links would be appreciated)

Welcome to Season 3, Episode 2 of Let's Talk. Here I am doing the last thing I thought I would do a couple of years ago: Dissecting the greatest player of this franchise. David Warner might have been our greatest batsman, Rashid might have been our greatest bowler. Against the test of time, there has stood only one player for the last 10 years as the franchise's flag-bearer: Bhuvneshwar Kumar. As the epitome of humility, dedication, and loyalty, Bhuvi has been associated with the franchise more deeply than anyone else in its history. But we are at a crossroads where doubts are seeping in about this great man. Why is that? I ask myself that question often. What made us lose confidence in Bhuvi? What is the actual turmoil he's going through? And is it ever really possible for him to regain his past self? We shall discuss everything in brief(oxymoron, judging by the length of this post). For the sake of the sanctity of the discussion, the stats I'll be presenting will pertain exclusively to his IPL career.
▫️The When:
When did he reach his peak? When did his downfall begin? What is this "When" supposed to mean? The question we should be asking is, when did we stop trusting in Bhuvi? Did it coincide with the onset of his injuries? Yes. Was it because of the injuries? No. Let me explain the differences. Bhuvi's IPL stats for SRH are 147 wickets in 133 matches at an average of 26.1, a strike rate of 20.6, and an economy of 7.62. Prior to the start of 2024, Bhuvi was four wickets away from becoming the first Indian player to take 150 wickets for a single franchise (a feat achieved by Bumrah). But that never came to pass due to a poor start to the season.
Bhuvi's career can be diverged into two parts: the 2014-17 period, which represented his peak, and the 2018-24 period, which represented his struggles. We will compare the statistics (especially those in the IPL and somewhat in T20Is) of these two phases to understand the two biggest phases of his career. This time period is not strictly quantified as a specific type of performance. He has had his struggles during his peak, while showing occasional brilliance during his struggles. Such is the life of a sportsman.
Now, the pre-2018 Bhuvi was India's best seamer across formats. It would be called a hyperbole, but I believed him to be so. Not only did he find his place in the longer format thanks to those fantastic IPL seasons in 2016 and 2017, but he also spearheaded the LOI bowling lineup with the then up-and-coming Jasprit Bumrah to absolute perfection. Bhuvi's defensive bowling gelled with the attacking bowling of Bumrah like fish to water, and it elevated the performance and status quo of both of them. The IPL seasons following the international ones were both the cause and effect. During this peak period, Bhuvi averaged a ridiculous 18.6 at a strike rate of 15.4 while maintaining an economy of 7.26. That meant he was taking wickets almost every two overs despite being primarily a defensive bowler. The dot ball percentage in the powerplay during this phase was an impressive 59.7%, while he was bowling two dot balls per over at the death (dot ball percentage in this period is 33.8%). Two overs at the start and two overs at the death were the fixed template for Bhuvi. The overs seemed insufficient when he was on song, and no wonder Dave respects him so much as a bowler. Every single fan who witnessed Bhuvi bamboozle Vohra in that immortal match against KXIP remains his fan to this day because it just feels right. So where did it all go wrong?
▫️The Why:
It all went wrong as soon as the greed of Indian cricket triumphed over the well-being of its premier pacer. The year was 2018, and there happened to be a pointless bilateral series against England. I'm getting too far ahead of myself. Let's add some more context to it. The year was 2014. Bhuvi ended that season with an exceptional tally of 20 wickets in 14 matches while maintaining an impressive economy of 6.66 at an average and SR of 17.7 and 16.0 respectively. Those are quite literally his best overall figures in any edition of the IPL, but the reality goes far beyond these numbers. Let's go back a little further and add some more context. Bhuvi debuted under MS Dhoni in 2012 against Pakistan. "Duh! We all know that! We see the highlights of it on DeathRattlePorn every other day." Despite having a great audition, Bhuvi wasn't considered a solution to India's long-running search for a generational seamer. Many considered him a generic swing bowler from UP with a paper-thin career. He was compared to Praveen Kumar and RP Singh, but never beyond. I won't be a contrarian and declare these opinions invalid because they were absolutely justified. For a couple of years since his debut, Bhuvneshwar remained strictly a new-ball bowler. MS Dhoni made sure to use up his overs at the powerplay and maximize the utilization of the conditions if they suited him. It suited Bhuvneshwar with his skill levels at that point and paved a path for him towards a red-ball debut (and that excellent series in England).
The trend set by MS carried over to the IPL as well. In the otherwise spectacular 2014 season, Bhuvi bowled 60% of his overs in the Powerplay, while trying his hand at the death in merely 26% of the total overs bowled. His economy at the Powerplay was 5.53 which skewed the overall economy to the lower side, while the economy was 8.96 at the death in this period, which despite not seeming much in the current scenario was in the bottom 38% percentile in that season (for bowlers bowling 10+ overs at the death). This version of Bhuvi was not far from the best version of him despite having the best stats. He did have a lean frame, and his speed barely crossed 135 kmph with an average speed between 125-130 kmph. It needed something more to make him stand out. In 2015, he gained slightly more muscle and tried to increase his speed. This was the first time in his career when he started bowling yorkers more frequently at the death while being more confident in bowling during this period. The gained muscle, however, attributed slightly to reduced consistency and accuracy, which resulted in the economy at the death being increased to 9.11 (highest during his peak) and a dot ball percentage of 29.2 (lowest during his peak). The encouraging signs, however, were the increased overs percentage at the death (37%), which showed that he was getting more and more confident in bowling at the death. Then came the crucial 2016 season, which changed the general public's perception of Bhuvi as a bowler. The Purple Cap did help the cause; the stats expectedly reflected his growth as a bowler. The death overs percentage was 32%, while the dot ball percentage at the death reached 35%. The overall dot ball percentage also reached a career-high of 47%. (In comparison, arguably the second-best bowler of the season, Fizz, had a death over dot ball percentage of 34 and an overall dot ball percentage of 42.) 2017 was the peak for Bhuvi, who was a lethal death bowler. It marked one of the most important seasons of his career in terms of skill development. He frequently used Yorkers and Leg Cutters (he used to be overly reliant on Off Cutters earlier), which ensured a brilliant Dot Ball Percentage (DB%) of 38 (a career high) while bowling 42% of the total overs during this phase. This was the absolute peak of Bhuvi's career. He won the Purple Cap for the second time, consistently clocked past the 140 kmph mark, and maintained clockwork accuracy over his lengths and lines. However, this season also saw a drastic decline in his powerplay wicket tally, raising concerns among the cricketing fraternity about whether Bhuvi was losing his natural swing in pursuit of pace.
These concerns became his worst nightmares in 2018. After coming back from his career-best overseas tour against South Africa, he suffered his first major injury, which would become the pioneer in a long string of injuries. The additional muscle mass was in question; some questioned the heavy workload he was subjected to as an all-format bowler, and some attributed it to his lack of natural fitness. Amidst all this, he was prematurely drafted in to play a meaningless decider in a bilateral series against England. This match is widely considered the undoing of Bhuvi's career in the long run, as not only was he unable to complete this match but also his injury was aggravated, and he was sidelined for a longer period than he was expected to be. His frequent injuries were an even heavier blow to the franchise, which meant they not only missed out on their best batsman but also had a question mark over the fitness of their best-ever bowler. This resulted in a stop-start season for Bhuvi in 2018, where he played in 12 out of 17 matches and finished with a career-worst average of almost 40. More than the numbers, his bowling style was questionable. He never looked 100% while bowling; the pace was down, he barely could extract swing from the pitch (while the most average opposition seamers managed to do it far better than him on the very same matches), and his accuracy at the death was more wayward as it had ever been. A seam bowler suffering from recurring injuries or immediately after a recent recovery is usually very cautious regarding his body, which prompts him to hold off on effort deliveries like yorkers and bouncers. Injury recovery and rehabilitation is more physical than mental. At times, despite recovering completely cricketers catch a knack of frequently injuries because they are not ready mentally. So without complete psychological recovery, even the greatest of comebacks can fizzle out like that. Bhuvi went down the same spiral. With the newly introduced knuckleball proving to be a decent wicket-taking option, he adapted slower balls as his go-to deliveries at the death while occasionally missing his lengths trying to hit the blockhole. The more he missed his lengths, the more he shied away from the delivery. At some point, bowling these slower balls became ingrained as his stock delivery at the death. Despite being hit for boundaries at the death after repeatedly bowling the slower balls (at varied lines, however), he still didn't have second thoughts about his increased predictability, which continued to cost him dearly. The injuries concerns playing at the back of his head and the severe lack of self confidence were painstakingly apparent. After months of battling through injuries, he reached a point where his body recovered, but his mind didn't.
Coming to the indirect factors, the modern-day game is meant to kill bowlers like Bhuvi. The balls barely swing anymore, and the pitches are as unresponsive as a girl to her toxic ex. (Can the seam bowlers be considered toxic exes, given how exploitative they were in the late 90s?) The boundaries are getting smaller, and new cricketing rules are being introduced every other day to rub salt in the injuries of these bowlers. The bowlers are fighting a losing battle, and the game demands only the freaks of nature to survive. Bhuvi, despite all his greatness, is a mere mortal. So as much as his own shortcomings have haunted him, he has suffered equally worse at the hands of the system and environment. With every injury, he found the ball to swing a little less. With every comeback, he was questioned about his range of abilities. The lack of confidence and self-belief this man has suffered, thanks to the inside and outside factors, can never be brushed out.
▫️The How:
How does he come out of that shell? Is it going to be magical? Is he going to wake up one day and turn the clock back? No! That's not how cricket works. He has already sorted out his frequent injury issues. For the last two years, he has maintained an average speed of 132-135. And these are not mutually exclusive events. He has sacrificed bowling effort deliveries in search of swing again. He's going back to his roots, and that's not necessarily a bad thing. At this point in his career, it's impractical to expect any drastic change in action or run-up. Fast bowlers are far too stubborn about that anyway. To find out the hows, we have to go back into the whys again. In the first 8 matches of this season, his line and length were all over the place. I use a particular stat as the Hittable Area bowled; shortened as HA% (the lower the better), to evaluate a bowler's consistency with his line and length. This HA% was staggeringly high for Bhuvi in these first 8 matches at 58%. That means he bowled a pressure-relieving ball every second ball. Not only did his wicket column suffer because of that, but he also was uncharacteristically expensive throughout different phases of the game. If you bowl 3 boundary balls per over, you are bound to go for 10 per over even if you get lucky on two balls.
In the last 4 matches, however, his HA% dropped to a mere 22%, and he was the only bowler whose HA% dropped during this period. (Nattu and Pat's HA% increased during this period.) I didn't have the time to go through all of the bowlers to draw a wider comparison, but the couple of bowlers I drew comparisons to (Bumrah and Harshal), despite having a better overall HA% than Bhuvi (16 and 34, respectively), ranked below him since this mini peak of 4 matches (Bumrah and Harshal had 27 and 31%, respectively). So this is the solution to his conundrum. The increase in control has brought out the best version of him, despite the current limitations.
Three overs in the powerplay should be given to Bhuvi irrespective of the conditions, and an over before the 17th over would not hurt his initial momentum. Like the match against RR, he can be occasionally trusted in crunch scenarios thanks to his experience. But the clearer his role is chalked out (as said earlier, going back to his roots as a defensive bowler), the more his confidence will flourish, which in turn will reflect in his bowling figures (as in the last four games). In the powerplay, however, it's paramount that he's paired with an attacking bowler who can operate as a strike bowler. Time and time again, Bhuvi has proven himself as an excellent setter(when the conditions are not inductive to his bowling style) in the powerplay for a more attacking bowler to take advantage of the pressure created by him. Otherwise, his spells are used up without any collateral damage to the opposition, and the initial pressure built up gets relieved consequently. (HELLO, 2018 FINAL!)
▫️Epilogue:
Bhuvi is at an odd conundrum in his career. His international career has been declared dead by the selectors and fans alike, despite having so much left to give. In his own franchise, there are barely any fans looking at him as a genuine retention choice. Part of it can be attributed to the inconsistenty and part of it can be attributed ironically to his very own essence. The understated, underrated, and hardworking guy who will never scream about his own value. To me, Bhuvneshwar Kumar personifies Sunrisers Hyderabad: understated, underrated, and hardworking, but forever hesitant to take the spotlight. For that very reason, I have always considered Bhuvneshwar Kumar is the greatest this franchise has ever seen. Nights will change, and the days will pass by. On some days, we'll feel shaky about Bhuvneshwar Kumar. On other nights, we'll declare him the King of the world. Such is his career graph at the moments. But SRH needs to make sure that he's never forgotten no matter how much the rest of the world tries to feign away from his existence(as they've already started to).
For he is SRH, and SRH is Bhuvneshwar Kumar.

Hey! So Id say I'm a pretty intermediate knitter and I've wanted to try and create a graph sweater without a pattern. The question I have is how do you take a graph and get the correct amount of stitches per row so that its the correct size needed but still looks like the intended picture. Is there a special way to measure or somethjng?? I've seen a lot of people successfully do this but they never say how they do it. And another question is would it be better to do it flat or in the round I'm fine with either but I've seen it done both ways and I would like to utilize the best technique. Thanks!

Hi everyone,
I'm curious to know which open source projects you have seen that have made the most ambitious attempts to push agentic behavior. I assume that most of these projects are currently failing, otherwise, we would all know about them already.
By ambitious attempt, I mean projects that involve a lot of complex elements, such as trying to reconstruct different types of human memory, complex context management, multishotting, MCTS, graph databases, reranking, etc. Large suites of tests examining long-running tasks are also important to try to make this thing possible.
I'm very certain that if, for example, GPT-4 level models were 1000 times cheaper than they are now, we would already have amazing agents. Maybe not entirely human-replacing, but certainly capable of replacing a lot of office jobs. When agents become commonplace, it might even become clear that creating relatively low IQ agents was possible with GPT-3.

Hey 👋
I'm looking at the possibility of creating a simple budgeting app that would help people understand where they are in their monthly budget in under a second.
I have followed this sub for some time, and I've seen people struggle with sticking to their budgets or maybe being overwhelmed with the complexity of tracking their income/outgoings.
There are a lot of budgeting apps out there, but I find that they are cumbersome to manage and I can't just open it up and see where exactly I am budget wise in the app without looking at numbers & graphs.
I've created a 4 question (anonymous) survey, it would be a great help if I could get some responses from the folks here who use a budgeting app 🙏
https://forms.gle/oWJ3ug6TC8fT3oBC8

Hello everyone,
I’m currently working as an Associate Backend Engineer and pursuing my Bachelor of Computer Application. I'm looking to enhance my skill set to improve my chances of getting a better job as I’m not satisfied with the pay at my current position.
Here are the skills and experiences I currently have:

• Backend Development: Created a payroll parser for streamlined data processing, integrated real-time communication systems using WebSocket, and designed/deployed diverse APIs with unit tests covered.
• Notifications: Implemented notification backends using technologies like Firebase Cloud Messaging for push notifications.
• Performance Optimization: Conducted load testing and API profiling to optimize and enhance system performance using tools like Locust and Django Silk.
• Development Practices: Introduced Behavior Driven Development (BDD), initiated automation testing using Selenium, and worked on transforming projects to multi-tenant architecture to improve scalability.
• Testing and Automation: Experience with unit testing, Pytest, BDD, TDD, and stress testing.
• Web Services and APIs: Hands-on experience with REST, GraphQL, and various async libraries.
• Containerization: Proficient with Docker (Images, Containers, YAML files).
• Cloud Platforms: Experience with AWS services such as EC2, S3, and SNS.
• Databases: Worked with PostgreSQL, MongoDB, Redis, and MySQL.

I would love to hear your suggestions on what other skills or technologies I should focus on to further improve my qualifications and make myself more competitive in the job market. Additionally, I’m looking for advice on how to find paid projects, search for remote jobs, or get paid for my skills. Any tips or resources you can share would be greatly appreciated.

My physics teacher once created a battery that he charged with a van de graph generator with two nails coming out of it. He charged it and it stored a ton of current. How did he do that? I assumed it was salt water but i can't find any way that would work.

I am creating my own images (Plots for my data) for my vision model and am wondering if:

1. Does the background colour matter? There is a lot of white space in graphs, so is it better to set it to black maybe? In RGB black is [0, 0, 0] and white is [255,255,255].
2. Are there preferential dimensions and/or dpi's that work particularly well?

MS-ISAC CYBERSECURITY ADVISORY
MS-ISAC ADVISORY NUMBER: 2024-054
DATE(S) ISSUED: 05/14/2024
SUBJECT: Multiple Vulnerabilities in Adobe Products Could Allow for Arbitrary Code Execution
OVERVIEW: Multiple vulnerabilities have been discovered in Adobe products, the most severe of which could allow for arbitrary code execution.

• Adobe Acrobat is a family of application software and Web services used to view, create, manipulate, print and manage Portable Document Format (PDF) files.
• Adobe Substance3D Painter is a 3D painting software that allows users to texture and add materials directly to 3D meshes in real-time.
• Adobe Substance3D Designer is a 3D design software that generates textures from procedural patterns inside node-based graphs.
• Adobe Aero is a cross platform solution that enables creatives with no coding and mininmal 3D experience to design, share, and view interactive augmented reality experiences.
• Adobe FrameMaker lets you create structured or template-based documents, review and collaborate with multiple content management systems and publish to a multitude of devices.
• Adobe Dreamweaver is a proprietary web development tool.
• Adobe Illustrator is a vector graphics editor and design software.
• Adobe Animate is used to create vector graphics and interactive content.

Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution in the context of the logged on user. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights
THREAT INTELLIGENCE: There are currently no reports of these vulnerabilities being exploited in the wild.
SYSTEMS AFFECTED:

• Adobe Acrobat DC 24.002.20736 and earlier versions on Windows and macOS.
• Adobe Acrobat Reader DC 24.002.20736 and earlier versions on Windows and macOS.
• Adobe Acrobat 2020 20.005.30574 and earlier versions on Windows and macOS.
• Adobe Acrobat Reader 2020 20.005.30574 and earlier versions on Windows and macOS.
• Adobe Substance 3D Painter 9.1.2 and earlier versions.
• Adobe Substance 3D Designer 13.1.1 and earlier versions.
• Adobe Aero 0.23.4 and earlier versions on Windows and macOS.
• Adobe FrameMaker 2020 Release Update 5 and earlier on Windows.
• Adobe FrameMaker 2022 Release Update 3 and earlier on Windows.
• Adobe Dreamweaver 21.3 and earlier versions on Windows and macOS.
• Adobe Illustrator 2024 28.4 and earlier versions on Windows and macOS.
• Adobe Illustrator 2023 27.9.3 and earlier versions on Windows and macOS.
• Adobe Animate 2023 23.0.5 and earlier versions on Windows and macOS.
• Adobe Animate 2024 24.0.2 and earlier versions on Windows and macOS.

RISK: Government:

• Large and medium government entities: High
• Small government entities: Medium

Businesses:

• Large and medium business entities: High
• Small business entities: Medium

Home users: Low
TECHNICAL SUMMARY: Multiple vulnerabilities have been discovered in Adobe Products, the most severe of which could allow for arbitrary code execution. Details of these vulnerabilities are as follows
Tactic: Execution (TA0002)
Technique: Exploitation for Client Execution (T1203):
Adobe Dreamweaver 21.3 and earlier versions on Windows and macOS.

• Adobe Animate 2023 23.0.5 and earlier versions on Windows and macOS.
• Adobe Animate 2024 24.0.2 and earlier versions on Windows and macOS.

Adobe Acrobat:

• Use After Free. (CVE-2024-30284, CVE-2024-34094, CVE-2024-34095, CVE-2024-34096, CVE-2024-34097, CVE-2024-34100)
• Out-of-bounds Write. (CVE-2024-30310)
• Out-of-bounds Read. (CVE-2024-30311, CVE-2024-30312, CVE-2024-34101)
• Improper Input Validation. (CVE-2024-34098)
• Improper Access Control. (CVE-2024-34099)

Adobe Substance 3D Painter:

• Out-of-bounds Read. (CVE-2024-30308, CVE-2024-30309)
• Out-of-bounds Write (CVE-2024-30274, CVE-2024-30307)

Adobe Substance 3D Designer:

• Out-of-bounds Read. (CVE-2024-30281)

Adobe Aero:

• Use After Free. (CVE-2024-30275)

Adobe FrameMaker:

• Heap-based Buffer Overflow. (CVE-2024-30288)
• Out-of-bounds Write. (CVE-2024-30291, CVE-2024-30290, CVE-2024-30292)
• Buffer Overflow. (CVE-2024-30289)
• Out-of-bounds Read. (CVE-2024-30287, CVE-2024-30286, CVE-2024-30283)

Adobe Dreamweaver:

• Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'). (CVE-2024-30314)

Adobe Illustrator:

• Out-of-bounds Write. (CVE-2024-20791)
• Out-of-bounds Read. (CVE-2024-20793)
• Use After Free. (CVE-2024-20792)

Adobe Animate:

• Out-of-bounds Write. (CVE-2024-30282, CVE-2024-30296, CVE-2024-30297)
• Stack-based Buffer Overflow. (CVE-2024-30293)
• Heap-based Buffer Overflow. (CVE-2024-30294)
• NULL Pointer Dereference. (CVE-2024-30295)
• Out-of-bounds Read. (CVE-2024-30298)

RECOMMENDATIONS: We recommend the following actions be taken:

• Apply the stable channel update provided by Adobe to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
  • Safeguard 7.1 : Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
  • Safeguard 7.2 : Establish and Maintain a Remediation Process: Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews.
  • Safeguard 7.6 : Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets: Perform automated vulnerability scans of externally-exposed enterprise assets using a SCAP-compliant vulnerability scanning tool. Perform scans on a monthly, or more frequent, basis.
  • Safeguard 7.7 : Remediate Detected Vulnerabilities: Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.
  • Safeguard 16.13 Conduct Application Penetration Testing: Conduct application penetration testing. For critical applications, authenticated penetration testing is better suited to finding business logic vulnerabilities than code scanning and automated security testing. Penetration testing relies on the skill of the tester to manually manipulate an application as an authenticated and unauthenticated user.
  • Safeguard 18.1 : Establish and Maintain a Penetration Testing Program: Establish and maintain a penetration testing program appropriate to the size, complexity, and maturity of the enterprise. Penetration testing program characteristics include scope, such as network, web application, Application Programming Interface (API), hosted services, and physical premise controls; frequency; limitations, such as acceptable hours, and excluded attack types; point of contact information; remediation, such as how findings will be routed internally; and retrospective requirements.
  • Safeguard 18.2 : Perform Periodic External Penetration Tests: Perform periodic external penetration tests based on program requirements, no less than annually. External penetration testing must include enterprise and environmental reconnaissance to detect exploitable information. Penetration testing requires specialized skills and experience and must be conducted through a qualified party. The testing may be clear box or opaque box.
  • Safeguard 18.3 : Remediate Penetration Test Findings: Remediate penetration test findings based on the enterprise’s policy for remediation scope and prioritization.
• Apply the Principle of Least Privilege to all systems and services. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. (M1026: Privileged Account Management)
  • Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
  • Safeguard 5.4: Restrict Administrator Privileges to Dedicated Administrator Accounts: Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user’s primary, non-privileged account.
• Restrict use of certain websites, block downloads/attachments, block Javascript, restrict browser extensions, etc. (M1021: Restrict Web-Based Content)
  • Safeguard 2.3: Address Unauthorized Software: Ensure that unauthorized software is either removed from use on enterprise assets or receives a documented exception. Review monthly, or more frequently.
  • Safeguard 2.7: Allowlist Authorized Scripts: Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute. Block unauthorized scripts from executing. Reassess bi-annually, or more frequently.
  • Safeguard 9.3: Maintain and Enforce Network-Based URL Filters: Enforce and update network-based URL filters to limit an enterprise asset from connecting to potentially malicious or unapproved websites. Example implementations include category-based filtering, reputation-based filtering, or through the use of block lists. Enforce filters for all enterprise assets.
  • Safeguard 9.6: Block Unnecessary File Types: Block unnecessary file types attempting to enter the enterprise’s email gateway.
• Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. (M1050: Exploit Protection)
  
  • Safeguard 10.5: Enable Anti-Exploitation Features: Enable anti-exploitation features on enterprise assets and software, where possible, such as Microsoft® Data Execution Prevention (DEP), Windows® Defender Exploit Guard (WDEG), or Apple® System Integrity Protection (SIP) and Gatekeeper™.
• Block execution of code on a system through application control, and/or script blocking. (M1038: Execution Prevention)
  
  • Safeguard 2.5 : Allowlist Authorized Software: Use technical controls, such as application allowlisting, to ensure that only authorized software can execute or be accessed. Reassess bi-annually, or more frequently.
  • Safeguard 2.6 : Allowlist Authorized Libraries: Use technical controls to ensure that only authorized software libraries, such as specific .dll, .ocx, .so, etc., files, are allowed to load into a system process. Block unauthorized libraries from loading into a system process. Reassess bi-annually, or more frequently.
  • Safeguard 2.7 : Allowlist Authorized Scripts: Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute. Block unauthorized scripts from executing. Reassess bi-annually, or more frequently.
• Use capabilities to prevent suspicious behavior patterns from occurring on endpoint systems. This could include suspicious process, file, API call, etc. behavior. (M1040: Behavior Prevention on Endpoint)
  
  • Safeguard 13.2 : Deploy a Host-Based Intrusion Detection Solution: Deploy a host-based intrusion detection solution on enterprise assets, where appropriate and/or supported.
  • Safeguard 13.7 : Deploy a Host-Based Intrusion Prevention Solution: Deploy a host-based intrusion prevention solution on enterprise assets, where appropriate and/or supported. Example implementations include use of an Endpoint Detection and Response (EDR) client or host-based IPS agent.

REFERENCES:

Hey Everyone.
I am currently struggling with a graph hbar and creating space between each bars.
The code i use:

forval j = 1/22 { separate andel, by(count_var != `j') veryshortlabel graph hbar andel?, over(count_var, label(nolabels)) over(komnavn, sort(mean) label(angle("") labcolor(70 79 85)) gap(25)) nofill name(P`j', replace) /// legend(off) bar(1, color(``j'' 173 80 121)) bar(2, color(99 122 122)) yscale(off) ylabel(,nogrid) ytitle("") blabel(bar, position(inside) format(%9,01fc) color(255 255 255) orientation(horizontal)) graphregion(color(none) margin(large)) plotregion(color(none)) graph export kom`j'.eps, replace drop andel? } 

The graph of the above code is on the picture
https://preview.redd.it/yozuw2hx8l0d1.png?width=1309&format=png&auto=webp&s=3fa08f469a410acd06acda95b466b54b1e1496bb
I have tried to add "bargap()" but that doesnt make any visual changes.

Hi everyone,
I’m Axel, a developer who has spent the past six months building PlusSales, an app to help Shopify store owners improve their conversion rates using Google Analytics 4 data.
Some of the features of the app include a Funnel Builder where users can create custom conversion funnels using the urls we provide which are taken directly from your store data. You can then edit and analyse your funnels to better understand where you lose customers, helping you to identify bottlenecks in your website's conversion funnel.
The second feature lets you request store reviews where the PlusSales team reviews your store, and gives you valuable advice on what to change and what to keep. We also give you grades for each section of your store as well as giving you great ecom stores to take inspiration from.
Another feature lets you view your GA4 data through graphs and tables, we also let your view your orders on a world map.
I launched PlusSales in April and am currently working on the third version, the app is 100% free as I hope to get more feedback and even some reviews on my app store listing. Please feel free to try it out and share your thoughts, you can find it on the Shopify App Store here:
https://apps.shopify.com/plussales
or look for PlusSales on the Shopify App Store.
I’d love to hear your feedback and suggestions. Thank you!

Hi everyone,
I’m Axel, a developer who has spent the past six months building PlusSales, an app to help Shopify store owners improve their conversion rates using Google Analytics 4 data.
Some of the features of the app include a Funnel Builder where users can create custom conversion funnels using the urls we provide which are taken directly from your store data. You can then edit and analyse your funnels to better understand where you lose customers, helping you to identify bottlenecks in your website's conversion funnel.
The second feature lets you request store reviews where the PlusSales team reviews your store, and gives you valuable advice on what to change and what to keep. We also give you grades for each section of your store as well as giving you great ecom stores to take inspiration from.
Another feature lets you view your GA4 data through graphs and tables, we also let your view your orders on a world map.
I launched PlusSales in April and am currently working on the third version, the app is 100% free as I hope to get more feedback and even some reviews on my app store listing. Please feel free to try it out and share your thoughts, you can find it on the Shopify App Store here:
https://apps.shopify.com/plussales
or look for PlusSales on the Shopify App Store.
I’d love to hear your feedback and suggestions. Thank you!

Hi everyone,
I’m Axel, a developer who has spent the past six months building PlusSales, an app to help Shopify store owners improve their conversion rates using Google Analytics 4 data.
Some of the features of the app include a Funnel Builder where users can create custom conversion funnels using the urls we provide which are taken directly from your store data. You can then edit and analyse your funnels to better understand where you lose customers, helping you to identify bottlenecks in your website's conversion funnel.
The second feature lets you request store reviews where the PlusSales team reviews your store, and gives you valuable advice on what to change and what to keep. We also give you grades for each section of your store as well as giving you great ecom stores to take inspiration from.
Another feature lets you view your GA4 data through graphs and tables, we also let your view your orders on a world map.
I launched PlusSales in April and am currently working on the third version, the app is 100% free as I hope to get more feedback and even some reviews on my app store listing. Please feel free to try it out and share your thoughts, you can find it on the Shopify App Store here:
https://apps.shopify.com/plussales
or look for PlusSales on the Shopify App Store.
I’d love to hear your feedback and suggestions. Thank you!

Hi everyone,
I’m Axel, a developer who has spent the past six months building PlusSales, an app to help Shopify store owners improve their conversion rates using Google Analytics 4 data.
Some of the features of the app include a Funnel Builder where users can create custom conversion funnels using the urls we provide which are taken directly from your store data. You can then edit and analyse your funnels to better understand where you lose customers, helping you to identify bottlenecks in your website's conversion funnel.
The second feature lets you request store reviews where the PlusSales team reviews your store, and gives you valuable advice on what to change and what to keep. We also give you grades for each section of your store as well as giving you great ecom stores to take inspiration from.
Another feature lets you view your GA4 data through graphs and tables, we also let your view your orders on a world map.
I launched PlusSales in April and am currently working on the third version, the app is 100% free as I hope to get more feedback and even some reviews on my app store listing. Please feel free to try it out and share your thoughts, you can find it on the Shopify App Store here:
https://apps.shopify.com/plussales
or look for PlusSales on the Shopify App Store.
I’d love to hear your feedback and suggestions. Thank you!