okhudeira
Joined 15 years ago
Karma
157
Submissions
65
Member since
Jun 6
https://omar.io
View on Hacker NewsRecent submissions
Comment · 2 years ago
Thanks. I did mean the latter or maybe the wariness has turned into weariness!
Comment · 2 years ago
I’m always weary of using abstractions like this. I understand the desire to simplify the process of creating new apps, but tools like this take an opinionated stance on how to couple and interact with all of these dependencies like Npgsql, meaning you might end up stuck with an older version of Npgsql until your Aspire package catches up.
Developers are also abstracted one more layer from their dependencies which isn’t always a good thing when debugging or for understanding how the dependencies work.
The manifest file seems like a step in the wrong direction. I see no reason to learn this .NET specific thing when I can learn to use docker-compose or the like.
The otel dashboard is nice but there are alternatives.
Comment · 3 years ago
All the discussions around header vs. path versioning reminds me of this post by Troy Hunt of Have I been Pwned.
> In the end, I decided the fairest, most balanced way was to piss everyone off equally. Of course I’m talking about API versioning and not since the great “tabs versus spaces” debate have I seen so many strong beliefs in entirely different camps.
https://www.troyhunt.com/your-api-versioning-is-wrong-which-...
Comment · 7 years ago
I think what you're doing with pulumi is the right answer and it's only a matter of time before this becomes the norm. The author's examples could easily be done with plain ol' JS/ES/TS with more far more extensibility and customization when the need arises.
I also feel this is where JSX got it right. Instead of creating yet-another-templating-language (looking at you Angular!), they used JavaScript and did a great job of outlining how interpolation works. Any new templating language is always going to be missing some key feature you expect out of a general programming language and your customers will continue to ask for more features.
Take for example Terraform and HCL, they're continually adding more and more [templating features](https://github.com/hashicorp/terraform/blob/master/website/d...) and [functions](https://www.terraform.io/docs/configuration/interpolation.ht...) because there's so many different ways to skin configuration/infrastructure as code. What if TF just expect a "computed" JSON object and it's left up to the developer to figure out how to put it together?
I'm gonna keep an eye on Pulumi and hope to be able to use in a real project soon.
Comment · 8 years ago
Marketing Attribution | Senior Frontend Engineer | Evanston, IL (with remote days) | Full Time | On Site | http://marketingattribution.com
Marketing Attribution was founded and is run by Ross-boy Link, a seasoned statistician and entrepreneur who’s been doing data science since before the term was coined. Ross continues to actively participate in the development of the product given his background in analytics and you’ll see him sling some SAS or Python to experiment with a new way to crunch numbers.
We develop and support highly automated analytical software that uses cloud-based statistical analysis of large marketing datasets to measure the incremental sales that result from various media, allocate marketing spend to the most efficient media, and connect to media buying systems to execute media buys.
In short, we take the client’s sales and marketing data, run analytics on it (our secret sauce), and from those results, tell the client where they should start and/or stop spending on marketing (TV, Radio, Internet etc.).
We're hiring our 5th engineer:
- Senior Frontend Engineer (http://marketingattribution.com/jobs/senior-frontend-enginee...)
You're coming in on the ground floor. This is an entirely greenfield project with no legacy code to maneuver around. The frontend was developed about 5 months ago and we're looking to accelerate the development of new features.
Comment · 8 years ago
Marketing Attribution | Senior Frontend Engineer | Evanston, IL (with telecomute days) | Full Time | On Site | http://marketingattribution.com
Marketing Attribution was founded and is run by Ross-boy Link, a seasoned statistician and entrepreneur who’s been doing data science since before the term was coined. Ross continues to actively participate in the development of the product given his background in analytics and you’ll see him sling some SAS or Python to experiment with a new way to crunch numbers.
We develop and support highly automated analytical software that uses cloud-based statistical analysis of large marketing datasets to measure the incremental sales that result from various media, allocate marketing spend to the most efficient media, and connect to media buying systems to execute media buys.
In short, we take the client’s sales and marketing data, run analytics on it (our secret sauce), and from those results, tell the client where they should start and/or stop spending on marketing (TV, Radio, Internet etc.).
We're hiring our 5th engineer:
- Senior Data Engineer (http://marketingattribution.com/jobs/senior-frontend-enginee...)
You're coming in on the ground floor. This is an entirely greenfield project with no legacy code to maneuver around. The frontend was developed about 5 months ago and we're looking to accelerate the development of new features.
Comment · 9 years ago
Marketing Attribution | Lead and Senior Data Engineer and Lead Frontend Engineer | Evanston, IL (with telecomute days) | Full Time | On Site | http://marketingattribution.com
Marketing Attribution was founded and is run by Ross-boy Link, a seasoned statistician and entrepreneur who’s been doing data science since before the term was coined. Ross continues to actively participate in the development of the product given his background in analytics and you’ll see him sling some Python to experiment with a new way to crunch numbers.
We develop and support highly automated analytical software that uses cloud-based statistical analysis of large marketing datasets to measure the incremental sales that result from various media, allocate marketing spend to the most efficient media, and connect to media buying systems to execute media buys.
In short, we take the client’s sales and marketing data, run analytics on it (our secret sauce), and from those results, tell the client where they should start and/or stop spending on marketing (TV, Radio, Internet etc.).
We're hiring our first engineers (#2, #3, and #4). Full description at:
- Lead Data Engineer (http://marketingattribution.com/jobs/lead-data-engineer)
- Senior Data Engineer (http://marketingattribution.com/jobs/senior-data-engineer)
- Lead Frontend Engineer (http://marketingattribution.com/jobs/lead-frontend-engineer)
You're coming in on the ground floor. This is an entirely greenfield project with no legacy code to maneuver around. You'll be responsible for building everything from the ground up.
Comment · 9 years ago
Related, here's a post by the author [1] about Evernote which sheds light on why he went about making this. Interesting read.
[1] https://medium.com/@mobitar/evernote-is-what-happens-when-yo...
Comment · 9 years ago
Author here.
I had no idea that this is a sensitive topic. I personally have family members that are civil engineers and understand the difficulty with acquiring a PE. I went ahead and modified the title.
Comment · 9 years ago
Author here.
Your response is a bit over the top. I'm in no way criticizing anyone or placing myself above anyone. I've been a junior engineer and I've under-engineered. I've been a mid-level engineer and I've over-engineered. Only through feedback from senior engineers did I finally get to see code I wrote stand the test of time 2 years later with minimal to no change.
As I mentioned in the post, no matter how many years we've been doing this, we'll continue to over-engineer and under-engineer because software is hard. The article is meant to layout the mistakes I've learned from, and for engineering managers, our responsibility is to help those we manage avoid the pitfalls we ran into.
Comment · 9 years ago
Your points couldn't be more accurate. In any organization, the quality of the function that dictates the work to be done (be it Product Managers or Business Analysts) heavily impact the success of an engineer's work. Some organizations choose to remove this level of management [1], others have ensure only former engineers fill this role.
It's very important but broad topic. I chose to not explore it in the post because it deservers its own discussion.
[1] https://www.quora.com/Does-Stripe-have-product-managers-or-d...
Comment · 9 years ago
I appreciate the feedback.
That's a very interesting article. However, it does seem suffer from the same issues Joel outlined, namely, the measure of attributes of a commit can be gamed and worked towards to achieve a "prolific" or "senior" status.
What the article you linked does reinforce is the value of iterative development. As opposed to doing large infrequent commits, doing small bits of work more frequently causes a success higher or "impact".
I would say that the article provides a data driven approach to justifying the effectiveness of good iterative planning. However, it doesn't address whether the commits of the "senior" engineer or the "prolific" engineer are of high quality.