I don't really see how anything other than being perfect stewards of Github works out in their favour.
772 karma · joined August 18, 2014
I don't really see how anything other than being perfect stewards of Github works out in their favour.
I'm not quite as cynical as the author of the OP when it comes to Microsoft's recent apparent change of direction, but who knows, that may just be naivety speaking.
Totally different ball game.
I fell into the trap of thinking that being more persistent in outreach would ultimately hurt more than it helped.
If you're in a society with suicide helplines, or social services that are affordable, I'd recommend reaching out to them for advice on how to get through to your friend. It's impossible to know how close to the edge he might be, but members of those organizations who speak to depressed or suicidal people on a daily basis may be able to provide you with advice on how to handle outreach, especially since he may not be reaching out to them directly.
It's unlikely that he will be open to engaging in a group situation. Reach out one-on-one, or visit in person.
Don't make the same mistake I did. My friend secluded himself out of the dumb idea that time apart would make his eventual suicide easier on his friends. It didn't, and there's nothing I can do now.
I've spent time in 5-6 different cities and towns and for sure, if you stay on main street it's very generic, or sterile. Rent a bike, set out in a random direction for 20 minutes; you won't find any TripAdvisor listings but the local culture is alive and well.
Most people expect to land somewhere new and have the local lifestyle at their fingertips, but that's not what the beaten track optimises for.
Being a stable bootstrapped small business is more worthy of respect than being an unstable underfunded startup, in my opinion.
Not that I have any idea how close 50,000 rubles would get you to a tank back then, but it seems she at least contributed to the cost of building it.
"Death march" as commonly used in English-speaking nations is typically used as hyperbole or dark humour, whereas in Japan "karoshi" is used in a clinical sense for documented cause of death.
That's what the person you replied to is talking about. Here in Vietnam, like Germany, they refill used beer bottles. You can tell a new bottle from old based on the scuff marks the machinery leaves on the glass, which build up over time. These are the "rings" the GP is referring to.
- Deployment: Every repo contains a "deployment" directory with a dir each for "staging" and "production" with all of the Kubernetes manifests (deployment, service, configmap etc.) necessary. Everything except secrets, which are managed manually. These declarative configs get applied to our cluster by gitlab-ci.
- ORM: You're probably not going to like this as a rails guy, but I've moved away from full, ActiveRecord-style ORMs. They don't work particularly well for my use cases and I enjoy the flexibility and control a thinner library like knex gives me.
- Background tasks: These are implemented as standalone apps running in our cluster, either as deployed workers subscribed to a Google Cloud Pub/Sub queue or scheduled jobs deployed using the Kubernetes cronjob functionality.
APIs: Express for basically everything HTTP. A lot more of our stuff is moving to PubSub for inter-service communication.
- Front-end templates: Everything is server-side rendered React. We run separate front and back end servers, scaled independently. The Kubernetes ingress handles routing to the SSR/React app and API app as necessary.
Mongo has its place, but its place isn't in most line-of-business applications for SMEs.
"Pick the right tool for the job" has been the biggest casualty in the midst of the schemaless hype we're going through right now.
I like the way it uses pull requests to handle drafts. A couple of clever build scripts in the repo would make for a pretty sweet deployment workflow.
I'm not super keen on the way it stores uploaded assets though. I understand the benefit of simplicity in only targeting a single API, but it would be nice to target a cloud hosting service (like GCE/AWS storage) for asset uploads.
The other options that did what I needed weren't as good, for other reasons.
Since I was going to have to write the code somewhere, I figured I'd fork the repo and maintain my own version. After I did that I realised my changes needed testing and documentation for other people on my team.
After that, a pull request was just a click of a button.
Saigon the wages can be a bit higher.
If you don't want to provide proof, don't make claims.
We've switched to Typescript for our React projects because we've found it's the sweet spot between developer perks (type checking, static analysis, intellisense, inline lint errors) and abstraction of the actual code running in production. It's also a lot less of a readjustment to make if you need to dive into the transpiled source to track down a subtle or unusual bug.
CSS modules are about 95% of the way to making this a solved problem.
Obviously this relies on imported components implementing CSS modules, but for a greenfield project this kind of thing works remarkably well.
So great to just push an ingress manifest and 10 minutes later suddenly get redirected to HTTPS.
You can npm install react-router@^3.0.0 and keep using what you know.
My biggest problem with Angular is the sheer surface area of the API and the dependencies between the different modules. Angular as a framework has 10+ different components, all of which are deeply integrated. All of this is wrapped up in Zone.js which produces some of the least helpful stack traces in history.
A React app may be a composition of 4-5 key libraries (state management, routing, authentication and potentially a form helper) but each individual library has a much smaller API surface area and the decoupling makes it easier to debug.
I recently rebooted a project that was built in Angular in React after over a week of trying and failing to debug a wide range of subtle issues in our implementation of universal rendering which absolutely broke AoT compilation. I won't deny that there's a high possibility that our code was the problem - it's just that there were no useful stack traces showing where to look and digging through the different libraries was a mission and a half.
There's a lot to be said for composing a few independent libs with small APIs, rather than having a gigantic framework whose documentation is only skin deep.