Many an engineer-designed page or screen would have benefited from some of the basic principles here, including "use more whitespace."
3,022 karma · joined March 7, 2012
A technologist, founder, and current Googler, I've repeatedly taken products from inception to commercial success across sectors, from startups to Fortune 10 companies. My specialty lies in bridging the gap between business vision and technical execution, deeply engaging with code and who mentors teams. Beyond engineering, I bring a global perspective from living abroad for nine years and speaking fluent French.
Get in touch with me: --------------------- @jlyman j @ joshualyman.com http://www.linkedin.com/in/joshualyman
[ my public key: https://keybase.io/jlyman; my proof: https://keybase.io/jlyman/sigs/c1xpV7dq3vEGU8gVObbZqSDE1_-E5t97Gl7HCQ98ebk ]
Many an engineer-designed page or screen would have benefited from some of the basic principles here, including "use more whitespace."
Very good summary of some of Ramsey’s big ideas though, thanks!
Average property tax rate for the Houston area is 2.31%. There's lots of things that come into the equation (homestead caps, exemptions, etc.), but for an average priced home of, say $350,000 you'll be owing ~$8,000 in property taxes.
The trickiest part is that your property values are reassessed every year, so for a long time our tax bill has just gone up, whether your income has or not.
I'll still take Texas economics over California economics, but everywhere has its tax pros and cons.
Another small plus: because if the rather unusual format of [myname].[mail|work], spam is virtually eliminated (at least in the .mail account).
I’d recommend it.
Do I hate that I used to pay a (large) one time fee for a version and now I've given them thousands of dollars more than I'd have preferred? Yes. Do I think this 12-month contract dark pattern is scummy? Yes. But I also can't find suitable alternatives either, so in a sense they've earned their money in that regard.
Seems like a great thing to have customers loving you enough to be bringing you new leads without any incentivization. Perhaps you could find other ways of thanking your good referrers in a more natural way (even sending them a box of chocolates or a personal outreach from the CEO to offer a one-time consultation session) that might go even further, be more flexible, and keep you from introducing new costs and problems.
As for changes during its lifetime, I would say that it is fairly on par for most web-focused frameworks, both front and backend. You could look at how ASP.NET has changed over the last few versions for example and see it being similar to React’s changes. The largest changes in React recently have been a greater focus on moving from syntactic sugar JS classes to pure functions, and React Hooks that go along with that. There’s definitely a shiny things syndrome you get if you just google for React tutorials, which is a bit annoying, but the official docs are pretty solid, and a few of the core devs are great to follow from a philosophical standpoint (like @dan_abramov).
Hope that helps!
[0]: https://insights.stackoverflow.com/survey/2021#technology
We had a set of static frontend apps (React) that were built in CI, and which had to support being served either out of S3 buckets in a variety of environments, or in walled-off on-prem environments, and therefore had to support a variety of API endpoint URLs. There was an 85% likelihood that the endpoint URL would be one main one (our primary distribution platform), but the other 15% could be anything.
I set up a global variable attached to `window` (gasp!) in the frontend's index.html that would point to the API endpoint, and by default our CI build would spit out the common scenario URL. When doing local development, the URL was supplied via an environment file, which worked perfectly.
For all other production scenarios we served the app out of a Docker container. At container launch, we passed in via env vars the proper endpoint URL, and a script would absorb the passed env var and embed it into the nginx config file using `envsubst` like the OP's article. This config file was configured using `subs_filter` to find our global variable in the index.html file and replace its contents with that of the env var, which was now hardcoded in a sense into the file.
This setup was a bit convoluted, but it allowed us to not have to change anything while in local development, be able to change the endpoint URL each time the container was launched without any rebuild, and didn't require any additional requests to a configuration script. It was the best fit in our situation to allow local development to continue unchanged while also supporting pretty much any future scenario.
Hope that might spur some ideas for someone.
Luckily for the majority sites on the Internet a CMS is exactly what's needed, and very often with more minimalistic custom development (plugins will take care of most of your needs). Thus with WordPress/Magento/Drupal being the heavyweights it's not at all surprising to see the statistics as laid out.
What I would love to see is a similar chart focused on bespoke applications, more like the kinds we would consider building for solutions, startups, and companies here in the HN space. I would guess it would probably hew closer to the stats in the TIOBE Index [0], but again one would want to filter specifically for web application development. Now those are some stats that would be very interesting!
(Though the autofill of SMS security codes in Safari is such a nice quality of life improvement! I’m betting it’s a private API, but man I want other browsers to implement it too.)
I have been served very well by wisely spending, or choosing not to spend, my innovation tokens on any given project. And the cap of 3 tokens really does seem to be a good level.
I won't be buying a Pixel, but I can certainly appreciate the fun the marketing team had with this one and I'll take it. :)
At Ikon Science we're pushing the boundaries of data visualization and exploration of well and wellbore data, especially in the browser.
On the Curate product team we're creating a full suite of applications to help scientists and operators discover, visualize, and understand their data. We publicly launched Curate in May, and it's a greenfield project where we get to leave legacy behind and focus on what works for modern software dev. So far we've created:
* data-heavy charts rendering at 60FPS
* interactive 3D visualizations of seismic data
* all tied back to GIS views of data on a map
We need to fill our growing team with a Senior Frontend Engineer who loves creating stellar data-heavy web experiences, with an eye for good UI/UX, a deep level of JavaScript expertise, and the ability to help mentor and train up a team through their experience, code review participation, and improptu mentoring skills.
Our tech stack:
* JavaScript / TypeScript
* React.js
* Redux
* ArcGIS
* Jest and Cypress
If you have expertise in some but not all of those that's fine, the highest preference is to solid React.js and JavaScript experience--we'll help you level up on everything else! We're all staying remote because we're scattered across the UK (and even me in the US), but there's an office in London where you are welcome to gather if you enjoy that work/life separation.
You can find the job page at [1], and you are more than welcome to email me questions or your CV by including "[HN]" in the subject (jlyman@ our company domain, see the link above). Can't wait to work with you!
[1] https://careers.ikonscience.com/jobs/1182214-senior-software...
HRAs on the other hand are a good vehicle for this.
EDIT: Ah, there is indeed an exception for continuation of coverage under COBRA which makes it acceptable to do so: https://dpath.com/hsa-and-cobra/
If you currently work for a big company (or really any company with >50 employees if I recall) you can qualify to take COBRA when you leave. Doing so is expensive, sure, but it's really usually about the same price as private insurance but much better (because it's a group plan). You can elect COBRA for up to 18 months, or 24 in some cases.
When COBRA runs out and you aren't yet in a position where you can have the organization you've founded pay for it, you can either look at joining a PEO or you can simply buy private insurance. Yep, it's definitely not great, but it is coverage. Additionally, if you are doing your own thing, look into setting up an HRA for yourself/your company--it lets the company pay for your medical costs without even when you're buying private insurance.
Not sure how to pay for it out of the gate when you might be pre-revenue for a while? You still have a couple of options. First, saving specifically for this use case makes a lot of sense. Even better, if you are currently in an HSA-compatible plan at work, max out the account for the year because you can use HSA savings to pay for premiums. Or if you have a spouse or SO and can hop on their plan for a while, good call too.
In general, and speaking from the position of someone who has spent far more time than I wish to admit building models and forecasting health expenses for when I was on private insurance and doing my own thing, it can be done. The freedom was definitely worth the price.
> 2019 Alexandre Borovik and Tony Gardiner This work is licensed under a Creative Commons Attribution 4.0 International license (CC BY 4.0). This license allows you to share, copy, distribute and transmit the work; to adapt the work and to make commercial use of the work providing attribution is made to the author (but not in any way that suggests that they endorse you or your use of the work).