colemorrison

9 ms·

31.
by colemorrison 7y ago
Having taught software, devops, and the like for years at this point, while this article touches on some difficult parts of teaching, they're all just side effects of bigger difficulties of teaching software. a) Everything is the &quot
32.
by colemorrison 8y ago
I agree if you have no idea what you're doing - which seems to be the case for many developers starting new projects stuck in the paradox of choice. But like anything else, if you understand the toolset, ecosystem, and have the experie
33.
by colemorrison 8y ago
In the "How it all started section" - > E explained that the main impetus behind the introduction of code review was to force developers to write code that other developers could understand; this was deemed important since code
34.
Using CloudFoundation to Build, Manage, and Deploy CloudFormation Templates(start.jcolemorrison.com)
3 points by colemorrison 9y ago|0 comments
35.
Show HN: CloudFoundation – make, manage and deploy large CloudFormation projects(github.com)
1 points by colemorrison 9y ago|0 comments
36.
by colemorrison 9y ago
Wow. Ya know, for every case this might "help" solve (workplace harassment and the like), I just can't help but say ultimately it will hurt far more. "But employers/managers/execs will operate more responsibly
37.
by colemorrison 9y ago
Aside from all of the usual hot fluff, I know some will disagree, but.. a) open source activity b) github activity c) active blogging on knowledge or topic related to dev The reason? Remote work takes a lot of independent work (obviously).
38.
5 Tips and Thoughts on Async / Await Functions(start.jcolemorrison.com)
1 points by colemorrison 9y ago|0 comments
39.
by colemorrison 9y ago
nah, I asked, it's for the amount reserved, not the amount used. https://twitter.com/nathankpeck/status/935930795864211461
40.
AWS Lambda vs. the World?(start.jcolemorrison.com)
2 points by colemorrison 9y ago|0 comments
41.
by colemorrison 9y ago
On one hand, I absolutely agree. The amount of change that happens for the sake of nothing more than change is laughable theme in front-end development. And if it's not for changes sake it becomes some weird squabble over how to best
42.
[Purple Security Squad Episode #8] IAM Securing AWS with J Cole Morrison(purplesquadsec.com)
2 points by colemorrison 9y ago|0 comments
43.
by colemorrison 9y ago
Fieldboom ( https://fieldboom.com/ ) | Senior Frontend Developer (React) | Remote | Contract to Full-Time Fieldboom is simple marketing software that helps you capture more leads and customer feedback so marketers / foun
44.
by colemorrison 9y ago
Yes yes, this is incredibly impressive. Very smart as well for ease of getting people to adopt the new version. I was fearing that I'd have to redo who knows how much just to use 16.
45.
Understanding AWS ECS and Docker – 10 Part Video Series(awsdevops.io)
1 points by colemorrison 9y ago|0 comments
46.
How I Select Frameworks and Tools for Development Projects(start.jcolemorrison.com)
2 points by colemorrison 9y ago|0 comments
47.
by colemorrison 9y ago
I had 2FA activated, changed phones and lost it. I couldn't log in to my account, so I contacted support. Within about 30 min they had put me back into my account. The dude who helped me was super chill and understanding as well.
48.
by colemorrison 9y ago
I've looked at GraphQL a number of times. Does anyone have any practical examples of integrating it with backend(s), APIs, and/or specific databases? So instead of "we use GraphQL, much love" + basic example and how it
49.
by colemorrison 9y ago
Shameless plug - I've got a 15 hour course on building a full infrastructure on AWS: https://awsdevops.io/p/practical-and-professional-devops-wit... We go from zero to fully scalable/loadbalanced etc. infrast
50.
Show HN: Practical and Professional DevOps with AWS and Docker(awsdevops.io)
2 points by colemorrison 9y ago|0 comments
51.
The Hitchhiker's Video Guide to AWS ECS and Docker(start.jcolemorrison.com)
5 points by colemorrison 9y ago|0 comments
52.
The Hitchhiker's Guide to AWS ECS and Docker(start.jcolemorrison.com)
3 points by colemorrison 9y ago|0 comments
53.
by colemorrison 10y ago
The base analogy - Building a VPC like building a Sim City - The AWS Account: The Landscape - The VPC: The City (Range of Postal Codes) - Subnets: Individual Postal Codes - Route Tables: The Road Infrastructure - Network ACLs: The Security
54.
AWS VPC Core Concepts in an Analogy and Guide(start.jcolemorrison.com)
3 points by colemorrison 10y ago|1 comments
55.
by colemorrison 10y ago
Without even having to dive into userdata or metadata, just (a) create the role for the ec2; (b) attach the trust and permission policies; (c) create an "instance profile"; (d) attach the instance profile to your target instances.
56.
by colemorrison 10y ago
Oh wow. That's an interesting case for inline policies. Now that I think about it, yes there's plenty of cases for reusable ones, and there seem to be just as many cases where a policy is unique to exactly that one service/
57.
by colemorrison 10y ago
Just for anyone wondering, as per joshpadnick's great suggestions, you can specify other AWS account's users/roles via Principal in a policy as well. Just use the other AWS account in the ARN. edit: if you want to do so via
58.
by colemorrison 10y ago
This is good stuff right here. Separate accounts can do tons. Also helps prevent stuff like dealing with VPC collision overhead.
59.
by colemorrison 10y ago
It's honestly going to depend. In some cases you don't really have a choice. For example if you want to limit an S3 bucket to an IAM group, since S3/Resource Policies don't support IAM groups ARNs in the principal, the
60.
by colemorrison 10y ago
Indeed, they're just a "resource" policy. They're still talked about and share the so many same attributes that it became more character saving to say AWS IAM Policies vs. AWS IAM, S3, SNS, SQS, Glacier Policies =P

More ›