That looks similar to BPMN
189 karma · joined June 26, 2013
What way if any will affect non US residents?
For bit of background about Turing’s life and efforts in WW2.
It’s not even necessarily experience because I see the experienced devs do this all the time. But your good developer will know that when the feature is so important that it needs “rushing”, aka straight to prod or, skip QA etc then that’s exactly the time to stand firm and write those unit tests instead of throwing crap over the wall and making it next weeks defect.
I think there’s a missing guide out there for people like myself who have an OO background, are looking to write some rust but can’t reconcile the borrow-checker with how they normally design software
I’d like to add that most black cab drivers make out like their card machine doesn’t work. It’s a total cash scam to avoid VAT. I’ve had a black cab deny picking me up before because I didn’t want taking very far (I had a twisted ankle and just wanted to shorten my walk home)
What style is that? The style of composing persistence technology, Authentication and Authorization, dependency injection, messaging, web communication etc to make a business application? If you know of a magical tech that doesn't aim to solve these problems in a standardized modular way so that the developer isn't socket programming from the ground up then please chip in.
"There are many moving pieces and many permutations of how they interact together."
Agreed. The problem space isn't todo apps or "Hotdog/No hotdog".
"It's practically impossible to understand it in its entirety, and thus impossible to guarantee that it's secure."
I don't understand the finer points of the myriad of TLS cypher suites etc, probably means I can't guarantee that they're secure. But what other option do I have? roll my own? Nope I'll take sensible defaults and twiddle the knobs where the client's requirements demand something different.
"You're basically plugging holes as you find them, but you're never sure that there aren't more holes you don't know about." - this is FUD.
The EE eco system while not perfect is basically a best in class for framework for everything we've learned about building business apps over the last 20 years.
But seriously, take a bet on a hip framework and it comes good (like react), good for you . But you can't cry when frameworks change API wildly when they clearly have a beta label on them.
This for me is a bad idea. I always have it in the back of my mind about reducing a modules footprint but as someone else mentioned on here. There's an art to it. Sometimes it's a bodge, followed by another fix in another part of the code base a month later which then frees you to delete.
Quite often it's like that actually. Patience is key.
I'd also like to add +1 for duplicating code. I see lot of devs just unwilling to dupe code at the cost of readability and speed of development.
Perhaps that code could be refactored down the line or more often the act of making it "neat" gives up 1 or more niceties that made you write it like that in the first place.
It's goes hand in hand with BDD and automated testing. I reckon there's a lot less people doing this stuff today in the wild than you'd think.
Sure there's the Netflix's n googles of the world. It was only a few years ago I would consult on projects that would have no CI. It happens.
The same thing is happening today, just because you read about kubernetes or swarm simply does not mean anything like the majority of the people out there are using it in production. Just go to a conference and and watch people stick their hands in the air.
Sure SOMEONE might have been doing continuous delivery back in 2005, it certainly wasn't me. I was too busy learning about data access objects vs ORMs and releases were 3 months away if you were lucky.
That said it can be useful sometimes to push changes out of band straight to a colleague. I have used this a few times to great effect but don't often come across the need
My colleague nudged me out of a stupor as I stared at the overhead projection. "Its Excel!" He whispered. "What are you on about?" I said. He was clearly mad. "The chart! He's done it in Excel". To my horror I began to see. This wasn't MS Project at all. It was subtle because the cells were so small they were almost no bigger than a pixel. I gasped and almost took the presentation off course.
It was like a mosaic. A feat. I've never seen anything like it since. Still baffles me how much effort he must have put in and the pain he must've felt every time that crappy plan inevitably moved to the right.
It can be listened like a podcast as each chapter is self contained and 10 mins or so with first hand accounts from actors etc.
Also, the article seems to think missing out some weak-ass graph and a link to wikipedia as irrefutable proof that this guy knows what he's talking about and everyone is out to misconstrue his words. Nope.
I'll tell you some bias he makes no mention of. The bias of having Disney princess for girls before they're born. Of being bought pink and told they're pretty not clever. Then getting dolls as presents instead of practical problem solving toys. The shoes and clothes bought that aren't practical for climbing trees or exploring. Then watching every Hollywood film about men while pathetic women characters look savvy and get "rescued" like the fairytales they were told when they were little.
After all this, even if the adverts of scantily clad girls in both boys and girls magazines haven't dissuaded them a career in science. Perhaps they study and perhaps they do so well as to get a job at google. Where they will be surrounded by a good many male asshole engineers (it's likely because I'm a male software guy and have seen no shortage). They persist anyway. Then some male privileged white lad who's a Princeton graduate pops up and says they're neurotic. Wants to talk bias in an open way? Nope
He's missed the point. He wants to talk about the very few who've travelled that unlikely journey made all they way to Google despite the obvious barriers that were in place before they were born.
All this has happened before. It will happen again
Maybe i'll write my open white paper,throw together some thinly veiled arguments, sprinkle some graphs and draw the conclusion that conservatives are total dickheads?
Not all you understand. Just biologically speaking. I'm not saying they are. I'm actually very pro conservative. But they are dicks right? I just want a debate in the open about some the evidence I can't be arsed to write. Maybe?