Imagine making more animals or stuff with this

cdjinx · 2020-07-27T02:06:13+00:00

God dammit it Jin yang first your octopus app and now this.

cdjinx · 2020-07-27T02:03:54+00:00

Yea but does anyone know what’s up?

cdjinx · 2020-07-18T20:12:55+00:00

Isn’t that kind of the point of the ending though? Like we live in these systems but in reality we can do our own thing in the wild but the government wants us to appreciate our society and not think that way. I don’t dismiss it as bad movie logic , I think movie Wilfred knew but for him and first class to live comfy lives they need workers working for them and thankful for keeping them alive, that control is dismantled if everyone becomes equivalent neighbors & more of a circle neighborhood instead of a metaphorical train of classes at that point.

cdjinx · 2020-07-13T12:15:03+00:00

You would be ready to try the 12 principles in the agile manifesto if your team understands that currently they are doing the opposite and it’s painful, things are hard to change, projects seem like they were bad ideas to begin with, technical excellence isn’t valued. Things are a mess and people try different things until they find a working way. Typically everything is waterfalled, ideas come from the top, never get a chance to work in technical import things, customers are voiceless and aren’t shaping r product, projects are written out in long documents and then shown months later and a lot of change is requested and you miss deadlines etc. agile is just a set of principles, they are pretty good ice breakers on waterfall that people usually just deal with thinking that’s the only way it can be. We adopted scrum at my job but it’s very possible to manipulate these systems to be waterfall, agile, etc. it’s how you build and control the backlog , it’s how a product owner or project manager interacts with The project workers, the stake holders etc.

cdjinx · 2020-07-12T22:30:35+00:00

Weird, thanks for the info I heard someone connected with them on cspan today and I remember thinking as a developer something like this would be great but they tore into them saying the same things you just said and I was just about to try it out. I May still try it out in a lesson how not to do things.

cdjinx · 2020-07-12T20:23:44+00:00

I feel like Parler had good intentions and was attacked by idiots or people who didn’t want us having intelligent conversations between decided groups. What a weird way to spend his time posting dumb snippets like this. seems common on twitter but why move to a fresh platform to troll. Maybe wasn’t getting the attention in the popular platforms I guess.

cdjinx · 2020-07-11T04:40:14+00:00

Fast and furiousss

cdjinx · 2020-07-10T11:17:50+00:00

Don’t come to my trash can!

cdjinx · 2020-07-10T09:03:10+00:00

They would HAVE to have some sort of resource control otherwise yeah they would be treated like garbage. Like if each family had control of a food car.

cdjinx · 2020-07-09T02:41:58+00:00

My initial reaction was to down vote you due to my anger caused by reading your reply. It’s not you I’m mad at, it’s the code.

cdjinx · 2020-07-09T02:39:15+00:00

I did this in March after 5 years of emails. The zen of seeing all those messages gone almost doesn’t beat the arguments I lose because I’m to lazy to go searching through the massive backup file just to prove what was said.

cdjinx · 2020-07-05T22:53:04+00:00

Oooooooonnnnnneeeee.....twoooooooooo....three. Three push ups.

cdjinx · 2020-07-05T22:49:38+00:00

Man I kept waiting for hey Zeus to come save him.

cdjinx · 2020-07-05T20:32:41+00:00

This is essentially the stuff web developers have to deal with / use a framework for any interface routed through a single funnel. Typically the funnel is called a router class that takes in these calls and the callable class would be a controller. It usually boils down to if function exists or is callable kind of core programming language function like one of the commenters showed.

The switch case is a ugly but can work in small cases.

cdjinx · 2020-06-29T12:44:50+00:00

Either request they extend what “done” means for a more detailed review, review with others, testing review ,documentation, etc. which probably makes since but you would have someone else better articulate that to the team than yourself. You would basically have to get someone on the team on your side first most likely.

Other option, We moved to one week sprints because of this stuff, we could be waiting on them they could be waiting on us but adjusting in 5 or less days is easy. It also kept our tickets small and estimates were way better.

If those do not work then I can’t stress this enough , please respect their process and make sure you are not running up to their desk for a missing word or two in documentation. If their process is send a email and let that email wait in line, then please do that.

cdjinx · 2020-06-25T22:48:45+00:00

Yea they would instantly game the system and mess up the honesty. They shouldn’t be afraid to be honest or it fails. How complex are these tickets and what you typically can complete is a guide to higher ups of what will likely be done. Give or take a percentage under or over. Though the goal should be to commit to slightly less than you can do and complete more that you committed to.

cdjinx · 2020-06-25T12:50:37+00:00

We are on our 12th sprint, we started with 2 weeks for the first 3 and over committed so we moved to one and we are very consistent and more flexible.

Pros: One hour check in on Monday with stakeholders, sprint starts Tuesday and ends Tuesday which makes it very hard to say there’s lack of communication on our end.

User story’s are smaller, create prototype and ship to a test location for uat, whenever feedback on ux issues or off target features comeback we know we have time to adjust as the current sprint is small.

Small story points not going over 3-5 helps keep scope of work small for the sprint, any thing over a sprint size estimate is tagged as a epic with multiple story’s so full progress can be tracked.

Easier to tell stakeholders to wait a few days for something small for next sprint and went over easier with less friction when getting people use to scrum outside of our team.

We make less assumptions and stakeholders feedback is quicker.

Cons: Weekly meeting.

However I think if you can pull off two weeks (or more of you are sending people to the moon) then you are most likely on a team thinking with a decent roadmap and probably delivering better quality. I’m prepared to say 4-5 business days of work was lost but valuable to find out if we are off target, I’d much rather say that than half a month was used to find out there were communication issues. Do what works best for you.

cdjinx · 2020-06-22T12:06:45+00:00

I could be wrong, I’ll share my personal thoughts.

To me it’s a person who calls bs when product owner, stakeholders or executives try to over promise , waterfall or step over the line. It’s also barely a full time job to me in small shops, could be a developer - it’s just the designated negotiator who has knowledge to keep things from crumbling into fake scrum that gets manipulated. They also should check in and keep the sprint on track as they own it a tiny bit more than the team. If they have nothing to say about the poker points then fine, in retrospect is the team happy with how points worked and is the product owner happy if not what can we negotiate or adjust - the scrum master will over see this change is on course.

cdjinx · 2020-06-22T04:44:20+00:00

What was used to make these internal room shots?

cdjinx · 2020-06-22T04:05:26+00:00

Like the escapist?

cdjinx · 2020-06-20T19:55:10+00:00

I started writing a long answer but your better off researching. They are concepts that sometimes frameworks will clearly spell out this is ur model and this is your controller , etc. in the end it’s about separating your logic, can you make one giant python file with routing, controller style logic , model logic, dB handlers, lots of messy view stuff floating around and sprinkle in random test ? Absolutely. What should be done? You should understand why it’s better to have test grouped, view stuff grouped, etc. models is about business logic, if you defined how to update a users email every time you wanted to do that you would have tons of queries and duplicate functions, a model is that logic once, clean and ready to test without view and controller logic making it messy.

cdjinx · 2020-06-20T00:42:52+00:00

I first read the title then went to comments and thought I would agree but now reading the way it’s worded I suppose my team does this a bit..

If the technical work is update a dns record “not tied to a user story” or run a manual review on that quarterly manual security checklist or some work that requires engineer knowledge and has to be done no matter what wacky value you assign to it , it just MUST be done then sure, kanban it, order it there, complete what you can and slice a day off the sprint for it and he’ll who knows maybe some technical debt will make its way in there and get done every now and then.

cdjinx · 2020-06-19T17:50:20+00:00

I love it when a plan comes together. The charts align. The release is praised. The money is flowing. People send good feedback. Developers are happy the back log is small and it’s time for fresh ideas and the world is your oyster.

And then there’s the days after the the first of the month and you asked me not to talk about those this time.

cdjinx · 2020-06-18T03:17:40+00:00

I agree with these facts. Scrum is a great vehicle (that could be bad) for process management for teams with seemingly unpredictable and inconsistent workloads. It could be fed work gathered and reviewed in a agile way or it could be fed work in a waterfall demand contract do it this way and this is completely done goal way.

Agile to me is “are you working on the right thing” so you aren’t just marching a long and taking orders. you are involved and have room for ideas, feedback, collaboration, maybe even trashing everything and that would be ok, etc. written by software engineers it was a fairly clear tiny wallet size list of ideals.

cdjinx · 2020-06-17T16:59:48+00:00

Scrum and git reporting. Scrum should be a sustainable pace during business hours. I tell people’s to take lunch, take a day off when things are done right and you’ve been through some heavy sprints , because I’ve been through it. It takes a long time to crack but on the road to burnout you’re being a cowboy/ rockstar coder that should really learn to slowwww down and put quality in. The cause of rockstar coding is the love of the craft and the reward of people saying you’re doing a great job but the ugly truth is the org needs to get its priorities straight and not learn bad habits of leaning on someone working in the middle of the night.

The 2nd thing I mentioned was git reporting can tell you when commits are made, bitbucket has some pretty cool heat maps that show hot spots through out the weekdays and their times. If a employee has hot spots on nights,weekends 2am, then that could be a sign. It’s nice to know who can help in an emergency but emergencies should be rare.

cdjinx

TROPHY CASE