Yea but lately i dont think my strengths are as a developer.

This fun one came up during code review today

https://www.amcharts.com/docs/v4/concepts/axes/

Gee what could possibly be wrong with code that looks like

Why do people do this??

Anyone from SoCal - I'm planning on going to this python meetup tonight. The other times I've gone it's been just a little talk about what you're working on and then people sitting around a couple tables working on their projects and chatting. (just like in the picture)

https://www.meetup.com/Girl-Develop-.../xfxhznyxcbtb/

uh... you're a girl?

In this case it means more like girl/women-friendly. The times I've been there it's run about 80% male. (just like in the picture)

Would love to join but 50 miles North from Irvine during rush hour sounds awful

I may go to this, especially if any of you OC UnhandledException regs want to go. I never really mind driving that much myself unless I've been doing a ton of it and I'm working from home at least 3 days a week lately, so I especially don't mind getting out.

https://www.meetup.com/OCPython/events/xrqfvnyzdbhb/

tbh I'd feel extremely uncomfortable going to a woman focused tech meetup but ymmv.

Yeah I can go to the OC one. I’m also in Irvine.

There's nothing woman-focused about it. It's just sponsored by a women's coding group and most of the people there are men. There's no talk about women's issues or anything.

Thats not what I meant, I'd just feel like I was intruding. Maybe its different here, my wife went to a similar meetup a year or two ago and said it was mostly women. Obv you would know better than me.

I know what you mean, and I'd kind of feel the same way. Women make spaces for themselves, and you'd like to let that happen the way they want it to.

At the same time, it's often hard to get a quorum. I get a lot of funny remarks about it, but I joined the Society of Women Engineers in college, because they didn't have enough women in the engineering program to form a local group. I maintained membership for a few years, along with ACM and IEEE until I stopped doing all of them.

(but also it sounds like this is a non-gendered group that is just organized by a women's group, so w/e)

I think the group just wants to make it clear they don't want any spectrum gamer-gater types who talk over women and dismiss them.

The meeting place is outside-ish in a covered area at a cafe and the rain had the attendance down. It was six people. One woman. Good thing for her some men showed up or it wouldn't have been much of a meetup.

Glad I went. One guy was a sysad (dev/ops) and he fixed up some configuration stuff for me.

For those of you who do react, do you use Node/Express for development and production?

Yea i actually just stood up a node/express/mongo(mongoose)/react app in under 24 hours.

If you know JS it's super easy.

unfortunately found it super hard to get create-react-app to hit an express server instead of webpack-dev-server so gave up and wrote my own ****ty webpack config.

This may be a dumb question, but it seems like Node/Express is building (possibly not the right term) a JS app for the client on the fly in development assuming you did the create-react-app stuff and aren't <script src=whateverreact>. Do you do that in production on the fly as well or do you do something that parses that and leaves static pure JS files on your server?

Hmm in my case the frontend is unnecessary and i only really need the backend to work, so I'm more just creating APIs but I dont see an obvious reason why c-r-a would care about anything except hitting a url. My c-r-a is gonna have no idea my server is express.

It's typical in a dev setup to have the app regenerated whenever the source changes, because that matches how people work. When you deploy you generally pre-package all your stuff into a set of .js files that are loaded by your site's index url. I really doubt apps that are served by express are generating the app on the fly.

Not sure I understand this question - express is just a normal webserver process that you start up and waits for HTTP events and responses with rendered html files etc. In production my react application is built/minified/bundled whatever and is served by express. Take a look at c-r-a's yarn build command vs its yarn start.

If you are just consuming APIs c-r-a is fine as you can use its proxy setting in development and then when you bundle it it will work deployed. Maybe. Like I said I had high hopes for c-r-a and ultimately couldn't make it work for my use case of express + socketio.

I dunno. The thing I'm actually wrestling with is sessions and cookies and thinking about how my dev app is running on the express server that I get when I create-react-app (dunno if I'm even describing that correctly) and in the app I'm making requests to a python API that lives somewhere else. And I'm wondering whether in production I'll be routing from my flask server to the JS that is currently the output of whatever Express (or babel?) does to turn React/jsx into plain JS. And then these sessions/cookies hostnames/CORS/whatever issues will all be different.

Yeah you're thinking of babel - it will turn your UI JS into a bundle of React, your users will hit your base Flask app which will serve your HTML and JS, then they will make ajax requests to your API. Flask (or something similar in python) should have a way to handle authentication/sessions etc. In JS/Node Express has similar stuff (Passport).

With react if you want to use actual urls for routing instead of hashes - when you deeplink you have to redirect those urls (IE - /registration) to the home page. So the server has to be in sync with that as well.

We found that out the hard way - trying to host our react app on S3/cloudfront. Normal navigation works fine, but deep-linking fails. The crappy workaround is to redirect 403s to the home page. Why cloudfront/S3 throws a 403 and not a 404 when say /registration can't find a file called 'registration' I have no idea.

But then you run into issues on stuff like our WAF for internal sites - the 403 gets redirected to home, which the WAF happily returns(!) to the outside world. Annoying - it doesn't load any of the supporting JS, CSS or img files. But you can still see the code for the home page for our dev site - which in theory might have some sensitive stuff that a dev doesn't realize they're exposing to the internet.

Fortunately our business doesn't care if we use hash routing - which I think is butt-ugly but it works around this problem. They may change their minds at some point though. "Um, can we get the URLs to look like this?" (shows normal URL with no hash) At which point I will give my boss the "I told you so" look. The fallback is either the hacky 403 redirect, or host the site on a real webserver on EC2.

Oh yeah - I messed around with statically generating the pages - with some package I forget the name. But then you still have to have .html in the url - which is even uglier imo.