With multiple searches failing despite advanced technology over the course of (more than) a decade, I personally think that it’s hard to believe MH370 will ever be found.
1,331 karma · joined February 25, 2021
With multiple searches failing despite advanced technology over the course of (more than) a decade, I personally think that it’s hard to believe MH370 will ever be found.
e.g. you init a project (`obelisq init`) and use `obelisq set -k <key> -v <value>` (e.g. `obelisq set -k SERVICE_KEY -v ABCDEF`) to set your environment variables:
OBELISQ_PUBLIC_KEY=0344ecbf96c3e01262402247b97231a22c0197d17121dd9c7d1b999faed1d54ac4
SERVICE_KEY=047ca044c1a59114246d5c5122ad1bdecfafa3c999fae5629181df54[...]
MY_SECRET=049072d4ffc233ed77f8d682d9fe3a75114987d496b06d44269600e8be[...]
When you run `obelisq generate`, code will be generated that allows you to do this: // `get` is type-safe, `mySecret` is number
// decryption of the value occurs when `get` is called
const mySecret= obelisq.get('MY_SECRET')
Partially inspired by my own article: https://www.carlos-menezes.com/post/type-first-configAlongside that, I've also been coaching kids (ages 4 to 11) at a local Benfica academy since September, and I've had a lot of fun helping them improve in many areas of the game. It's a truly enriching experience.
I think they look at Vercel and see they're making a good buck with similar offering.
With English not being my native tongue, it gets difficult to speak some words at times and I have to reshoot each takes several times. But it's worth the effort and it's different to what I do in my main channel!
Early on, most time goes into writing new code, with some design docs if the team is structured — this is as simple as writing a README.md or having a static documentation website.
Once you have users, writing new features slows down, and more time shifts to bug fixes, refactoring, and keeping things running. In startups, this transition happens later since growth takes priority. I haven't worked for any large companies yet but I assume they tend to balance maintenance earlier.
Location: Portugal
Remote: Preferred
Willing to relocate: No
Website: https://carlos-menezes.com
Technologies: TypeScript/JavaScript, C++, React, Redis, AWS, Postgres, MongoDB, Knex, Objection.
Résumé/CV: https://carlos-menezes.com/cv.pdf
Email: talk@carlos-menezes.com
LinkedIn: https://www.linkedin.com/in/cmenezes1998/
Hello! I have been passionate for programming since the age of 8 when I began tinkering with websites.I have now 3 years of professional experience building applications as a full stack engineer, mostly using TypeScript and many different frameworks and tools. I am comfortable with a wide variety of technologies and always eager to learn new ones.
Location: Portugal
Remote: Preferred
Willing to relocate: No
Website: https://carlos-menezes.com
Technologies: TypeScript/JavaScript, C++, React, Redis, AWS, Postgres, MongoDB, Knex, Objection.
Résumé/CV: https://carlos-menezes.com/cv.pdf
Email: talk@carlos-menezes.com
LinkedIn: https://www.linkedin.com/in/cmenezes1998/
Always happy to meet people and open for new job opportunities.1. Create an implementation of the `Transport` class (you'll only have to implement the `handle` method);
2. Add to the list of transports on your `Logger` instance.
This is still a major work in progress. The question has been asked many times on other communities and I agree that there should be a section on the README (maybe at the very top) comparing this with other loggers (e.g. how transports work in Caran vs Pino, benchmarks, etc).
It's something I have considered but I've been fleshing out transports asap.
All the best!
Location: Portugal
Remote: Yes
Willing to relocate: No
Technologies: TypeScript, JavaScript, Rust
Résumé/CV: https://carlos-menezes.com/cv.pdf
Email: talk [at] carlos-menezes [dot] com
Github: github.com/carlos-menezes"Hi,
Many of our community members were justifiably frustrated that Bridge was replaced by an alternative that did not meet their needs. We heard your feedback and decided to bring back the option to get Megascans content via Bridge and Quixel.com. This should allow you to build up your own library of Megascans in Bridge and on Quixel.com, so you can later on enjoy it via the Bridge workflows you know and love.
Starting today, legacy Megascans library acquisitions are again available through Bridge and Quixel.com until December 31, 2024. Anything that you claim until the end of the year you can use immediately and continue to use after January 1, 2025. You can now claim the legacy Megascans library for free under the Epic Content License and we will offer a one-click solution to claim all the assets at once next week."
Literally my first internship. Had to migrate a small system from C to (modern) C++ in the span of 6 months. Most files (and I'm going to say in the ballpark of 85%) had last been touched in 2003.
I started my intership in 2020.
"Apple severed ties" repeats.