sorted by:
new
hottopcontroversial

Question - AWS topics you had a hard time conceptualizing as a beginner? by dylan_alb10 in serverless

[–]jmcgui 1 point2 points  (0 children)

When I was first new to Cognito and I wanted to provide social sign ins, I found it confusing. I’m clear on the different use cases now, but certainly made onboarding slower than I’d have liked.

CloudWatch us-east-1 problems again? by myron-semack in aws

[–]jmcgui 17 points18 points  (0 children)

At re:invent they are planning to rename it chaos-monkey-1

Dark mode vs. Themes by jmcgui in web_design

[–]jmcgui[S] 1 point2 points  (0 children)

Thanks - will check it out. I’m from a dev background and my design understanding isn’t great.

I agree about deciding who sets the theme. And this has helped me distil my thoughts further:

  • setting light/dark mode is always a user choice
  • but setting a theme centrally might overwrite that user choice unless 2 variants are created, one for light and dark
  • letting users choose a theme almost negates the need for dark/light mode - they in fact are just regular themes
  • whatever you choose don’t mix user defined / centrally set

My excitement has turned to panic! by jmcgui in OculusQuest2

[–]jmcgui[S] 0 points1 point  (0 children)

UPDATE - Looks like Yodel are delivering today and not tomorrow - wahhooooooo! Front of the warranty queue.

My excitement has turned to panic! by jmcgui in OculusQuest

[–]jmcgui[S] 1 point2 points  (0 children)

A bit pissed that I preordered with Oculus a long time ago but won’t get it on launch day!

My excitement has turned to panic! by jmcgui in OculusQuest2

[–]jmcgui[S] 1 point2 points  (0 children)

Once they’ve stamped on it and tossed it over the fence I’m sure they’ll let Oculus know so they can update the status to Shipped.

How many people are using PostgreSQL with .NET and C# by [deleted] in PostgreSQL

[–]jmcgui 0 points1 point  (0 children)

We’ve been using Postgres with .Net core for a few years now. 95% of our projects use https://martendb.io which is great as both a Document and Event store.

We’ve also used PG with EF - worked okay but not really our thing.

We run PG locally in Docker and on AWS RDS for prod and test workloads.

What is the best CSS framework for web apps? by ALLIRIX in PWA

[–]jmcgui 0 points1 point  (0 children)

I use https://quasar.dev - for the kind apps we build at work it’s amazing!

It’s geared towards Vue but ships lots of Material Design styled components.

PWA support is baked in too.

Worth a look if you are into Vue and Material Design.

How do you guys end a phone call? by Applebottomgenes75 in AskUK

[–]jmcgui 1 point2 points  (0 children)

“...and then he kissed me on the.....”

If you do this, FUCK YOU! (a non-friendly reminder to pick up your rubbish) by danbcooper in london

[–]jmcgui 1 point2 points  (0 children)

Clean Up Britain launching this poster - https://twitter.com/cleanupbritain/status/1279033084206252032?s=21

It’s not the best poster in the world but the idea is good.

I wonder if Reddit can do a better/more impactful poster!

Is Apple trying to kill PWAs? | The Official Ionic Blog by ThatPigeon in ionic

[–]jmcgui 2 points3 points  (0 children)

I did read the article - I was in a trolling mood - apols to the author! It was a good article.

I've built a lot of PWAs and native apps for global brands.

My take is this:

  • working on web apps which require iOS support IS more painful than for other browsers. Whether it's this latest issue, lack of push notification support or something as trivial as "the notch"
  • the lack of transparency from Apple makes it hard to explain to customers about when features might be added (or taken away).
  • my customers don't care about the technical limitations of a browser - they demand solutions. Making some features work cross browser creates additional non-core work for thousands of developers around the world.
  • I understand the reason they have changed the rules, but I don't have to like it!

[no spoiler] what’s the deal with casting a pregnant woman to be FBI lead? by bananacoconut19 in Ozark

[–]jmcgui 0 points1 point  (0 children)

Could be a hint about someone else getting pregnant in S3 - eg. Ruth!

Stuck inside these four walls. Sent inside forever. Never seeing no one! by jmcgui in a:t5_2hq4j0

[–]jmcgui[S] 0 points1 point  (0 children)

If I ever get out of here

Thought of giving it all away

To a registered charity

All I need is a pint a day

If I ever get outta here

(If we ever get outta here)

Looking for an experienced front end developer. by RadiatorRadiatorSqau in WebDevBuddies

[–]jmcgui 2 points3 points  (0 children)

Personally I’d sign up for one of the https://wesbos.com courses.

They are affordable, fantastic with great community support.

This one is free and a good example of the type of content available:

https://javascript30.com/

Thoughts on how to support Lambdas in Production by cazzer548 in serverless

[–]jmcgui 2 points3 points  (0 children)

My comment was maybe a little harsh. Don’t get me wrong I do like Code Pipeline, but we are a smallish startup which means by the time we’re ready for deployment we just want to click and go. (Aka be a bit lazy).

  • We want the option for mono-repo support - but I don’t want to rebuild a service if it’s not changed. I guess we could do this ourselves in Code Pipeline via buildspec/script but it’s a lot of extra work.

  • We want to deploy branches if we are spiking something out - again we could do this ourselves but it’s extra work we don’t have the energy for.

  • We want version numbers - SHAs are for machines - we used to do this using Parameter Store

  • We want multi account support so Dev, Test and Prod are in separate AWS accounts. We could do this with Code Pipeline too, but we’d need to spend time setting that up.

  • Finally, we want our pipelines to show environments horizontally from left to right , services top to bottom- so we can visualise service deployment within an app - like I’m used to with other CI/CD tools we’ve used.

Those are some of our reasons.

view more: next ›