Another update on my brushless pistol
Showing a look at some of the kinds of stuff/problems I wish I saw more of when I started out designing
Showing a look at some of the kinds of stuff/problems I wish I saw more of when I started out designing
I've included a screenshot of my heat settings in a screenshot. This happens no matter what my material is; my latest print is Bambu SilkPLA+, but normally I use Protopasta HTPLA. Same exact effect, though -- warped corners, plus the first half inch of the print deforms inward.
Printer: Bambu A1 (located in a non-temp-controlled garage)
Filament: Babmu SilkPLA+ and Protopasta HTPLA.
Nozzle temp: 230
Plate temp: 65
The prints take a long time (the one in the pic took about 15 hours), which I'm sure makes a difference, but I don't know how.
side-by-side with a Gnk-200 for scale
While I figure out why my 250 fps blaster loses so much voltage when it spins up, I started working on fixing my old pistol project. This is basically taking the internals of the MS-GnK and condensing them down into the size of a GnK-200. It'll hit around 200 fps on two stages of 1404 6000KV wheels. I consider it the half dart version of a speedsoft hi-capa: designed for indoor-type pushing and run 'n gun.
...but nobody thought to photograph Dante hitting the Piccolo pose???
https://www.printables.com/model/1748744-brk
I know that there are dozens of talon mag holders out there, but I wanted to give it a shot, looking to make one that wouldn't wobble when I ran around -- enough of me wobbles when I run already!
It uses ball detents for a very satisfying click when you insert and pull the mags. It's also designed to be as low-profile and no-frills as possible, but people are welcome to remix as they see fit.
First firing test on lowest setting (120 fps)
Got my blaster built, and somehow in the jostling of all the wiring while getting it all to seal up, the battery reader won’t work, which means it won’t fire.
I’m a first-time Project Coordinator, hired to help coordinate an Operations department at an insurance brokerage. Our department has three arms, two of which require active project management, which I was hired to do. I am technically at the bottom of the hierarchy, meaning everyone’s my boss, which means that I bounce between having to make everyone happy.
My director asked me to pilot some PM software (ClickUp), because they were concerned that there isn’t any buy-in to the existing PM structure (a labyrinthian mix of MS Lists, PowerBi dashes, and personal checklists squirreled away in decentralized locations. I’ve spent about a month migrating data to ClickUp, and have been trying to recreate dashboards and/or give my director more visibility to the entire department.
There’s concern about giving my director too much granular detail from one of my managers (ranked directly below my director). The manager doesn’t really like strict PM styles, which is totally doable: I just need to show how far along a project is to my director, so the director can show the VP. My manager wants to have lists with generic milestones (which is perfect, tbh — it makes it easy to visualize), but when it comes to all the tasks making up those milestones, my manager doesn’t want to have those on the official ClickUp pages, but instead keep those on team-only checklists on places like MS Planner. This kind of runs counter to what I’ve been asked by my director, who wants to know why Associate X can’t seem to get ahead on their assigned work; I need those tasks (and a difficulty rating to boot!) to show which Associates are behind, and what their workload looks like.
Is this common for PMs to deal with? I really like and need this job, and need to walk this tightrope so I don’t get canned for incompetence or get canned for not being able to read the tea leaves of my department. Could anyone give me some advice on what to say/do, please?
It’s not like they run on D batteries, right?
I'm a Project Coordinator whose position was created for me when I was recently hired. I work for the Operations department of an insurance company's main financial hub. While we're called Operations, it's more of a catch-all for projects involving compliance, process improvement, and outsourcing management. Those three arms all act independently (and sometimes interdependently) of one another, but report to the same director. I was hired to help the director keep track of/report on activities across these arms.
My first coup was getting the VP to give us licenses for PM software. Projects until this point had been managed on a combination of Excel, MS Lists, PowerBi, Planner, and other one-time use applications. There was no visibility across the department, because each arm hated the other's system/tool and refused to use it. I'm in charge of bringing all the project trackers under one umbrella.
The main issue I'm having is that two of the arms don't really follow (or need to, for that matter) follow a traditional project management process, but the third runs a pretty rigid Scrum-style process. I'm new to PM work -- this is my first job -- so I'm perhaps a little overly open to receiving advice from people who want to be helpful. The third arm wants me to deploy the exact same rigid Scrum across the entire department, and don't understand why it can't be done (because of course, they can't see the other projects going on that aren't theirs). The other two departments don't really need a rigid system so much as they need their myriad checklists brought into one place. I'm more concerned, and more importantly, the director is more concerned with gaining visibility and seeing overlap than with everyone using the same rubric. I personally don't see how Scrum will benefit teams who handle continuously repetitive tasks as opposed to delivering products/tools/dashboards/etc., which makes sense to have a more disciplined approach.
Bottom line: it's my job to set up the PM framework, but am I wrong in thinking that different teams/project types require different types of management? I don't want to shoehorn extra admin tasks on teams who are working just fine with "fancy checklist" management, but is this a wrong take?